Skip to main content
Mallory
MediumVulnerability

CVE-2019-2691: Denial of Service in Oracle MySQL Server Security Roles

Published Apr 23, 2019 · Updated 3 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
EPSS1.9%80th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Red HatOracle Corporation
IdentifiersCVE-2019-2691CWE-269

CVE-2019-2691 is a vulnerability in the Server: Security: Roles subcomponent of Oracle MySQL Server, affecting supported MySQL 8.0 releases through 8.0.15. A highly privileged attacker with network access through multiple protocols can cause the server to hang or repeatedly crash, resulting in complete denial of service. Exploitation has low complexity and requires no user interaction. The underlying defect and vulnerable function are unspecified.

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 causes complete loss of MySQL Server availability through a hang or frequently repeatable crash, disrupting applications dependent on the database. No confidentiality or integrity impact is identified. The CVSS 3.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.

Mitigation

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

No specific workaround is documented. Until patched, restrict MySQL network access to trusted, authorized high-privilege administrative users and limit access through exposed MySQL protocols.

Remediation

Patch, then assume compromise.

Apply the applicable vendor security update addressing CVE-2019-2691. For Red Hat Software Collections on RHEL 7, install the update supplied by RHSA-2019:2484. For the MySQL 8.0 module on RHEL 8, install RHSA-2019:2511. Both updates upgrade MySQL to version 8.0.17 and automatically restart the MySQL server daemon, so plan for the associated service interruption. Oracle addressed the issue through its April 2019 Critical Patch Update.

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
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-2691 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2691 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2691?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2691.
Is there a patch for CVE-2019-2691?
Apply the applicable vendor security update addressing CVE-2019-2691. For Red Hat Software Collections on RHEL 7, install the update supplied by RHSA-2019:2484.
What products are affected by CVE-2019-2691?
Oracle Corporation Mysql, Red Hat Enterprise Linux Eus, Red Hat Enterprise Linux Server Aus, Red Hat Enterprise Linux Server Tus, Red Hat Enterprise Linux, and 1 more.
How severe is CVE-2019-2691?
CVE-2019-2691 has a CVSS v3.1 score of 4.9 (Medium) and an EPSS score of 1.9% (80th 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.