Skip to main content
Mallory
MediumVulnerability

CVE-2019-2606: Privileged Denial of Service in Oracle MySQL Server Security: Privileges

Published Apr 23, 2019 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.9Medium · v3.1
EPSS2.1%82nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Red HatFedora ProjectOracle Corporation
IdentifiersCVE-2019-2606CWE-269

CVE-2019-2606 is a denial-of-service vulnerability in the Server: Security: Privileges subcomponent of Oracle MySQL Server, affecting supported MySQL 8.0 releases through 8.0.15. A highly privileged attacker with network access through supported protocols can cause the server to hang or repeatedly crash. The vulnerable function and underlying defect are unspecified. Exploitation has low complexity and requires no user interaction. The CVSS v3.0 base score is 4.9, with vector CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can completely disrupt MySQL Server availability by causing a hang or frequently repeatable crashes, interrupting database access for dependent applications. The CVSS assessment identifies high availability impact, no confidentiality or integrity impact, and unchanged security scope.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict MySQL network access to trusted administrative hosts and minimize assignment and use of high-privileged MySQL accounts. Monitor for unexpected mysqld hangs, crashes, and restarts.

Remediation

Patch, then assume compromise.

Apply vendor updates addressing CVE-2019-2606. Red Hat supplied fixes through RHSA-2019:2484 for Red Hat Software Collections on Enterprise Linux 7 and RHSA-2019:2511 for the MySQL 8.0 module on Red Hat Enterprise Linux 8; both updates upgrade MySQL to 8.0.17. Installation automatically restarts the MySQL server daemon, so account for the service interruption during deployment.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Fedora ProjectFedoraoperating_system
Oracle CorporationMysqlapplication
Red HatEnterprise Linux Eusoperating_system
Red HatEnterprise Linux Server Ausoperating_system
Red HatEnterprise Linux Server Tusoperating_system
Red HatRed Hat Enterprise Linuxoperating_system
Red HatSoftware Collectionsapplication
FAQ

Frequently asked questions

Is CVE-2019-2606 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2606 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2606?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2606.
Is there a patch for CVE-2019-2606?
Apply vendor updates addressing CVE-2019-2606. Red Hat supplied fixes through RHSA-2019:2484 for Red Hat Software Collections on Enterprise Linux 7 and RHSA-2019:2511 for the MySQL 8.0 module on Red Hat Enterprise Linux 8; both updates upgrade MySQL to 8.0.17.
What products are affected by CVE-2019-2606?
Oracle Corporation Mysql, Red Hat Enterprise Linux Eus, Red Hat Enterprise Linux Server Aus, Red Hat Enterprise Linux Server Tus, Fedora Project Fedora, and 2 more.
How severe is CVE-2019-2606?
CVE-2019-2606 has a CVSS v3.1 score of 4.9 (Medium) and an EPSS score of 2.1% (82nd percentile) as of Nov 14, 2026.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.