Skip to main content
Mallory
MediumVulnerability

CVE-2019-2810: Denial of Service in Oracle MySQL Server Optimizer

Published Jul 23, 2019 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS4.9Medium · v3.1
EPSS2.0%81st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Red HatOracle Corporation
IdentifiersCVE-2019-2810CWE-400

CVE-2019-2810 is a denial-of-service vulnerability in the Server: Optimizer subcomponent of Oracle MySQL Server, affecting supported versions 8.0.16 and earlier. A highly privileged attacker with network access through multiple protocols can cause the server to hang or crash repeatedly. Exploitation has low complexity and requires no user interaction. The specific vulnerable function and underlying weakness are unspecified. The CVSS v3.0 base score is 4.9 (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 causes complete denial of service of the affected MySQL Server through a hang or frequently repeatable crash, disrupting database availability. The CVSS assessment identifies high availability impact, no confidentiality or integrity impact, and unchanged scope.

Mitigation

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

No vulnerability-specific workaround is identified. Pending patching, restrict network access to MySQL to trusted systems and limit highly privileged database accounts to necessary administrators. These measures reduce exposure but do not correct the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade to MySQL 8.0.17 or a later vendor-supported release containing the fix, or install the applicable distribution security update. Red Hat provides fixes through RHSA-2019:2484 for Red Hat Software Collections on RHEL 7 and RHSA-2019:2511 for RHEL 8; these updates automatically restart the MySQL server daemon. For affected Unity Linux 20 installations, update the mysql package in accordance with UTSA-2026-153626.

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-2810 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2810 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2810?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2810.
Is there a patch for CVE-2019-2810?
Upgrade to MySQL 8.0.17 or a later vendor-supported release containing the fix, or install the applicable distribution security update. Red Hat provides fixes through RHSA-2019:2484 for Red Hat Software Collections on RHEL 7 and RHSA-2019:2511 for RHEL 8; these updates automatically restart the MySQL server daemon.
What products are affected by CVE-2019-2810?
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-2810?
CVE-2019-2810 has a CVSS v3.1 score of 4.9 (Medium) and an EPSS score of 2.0% (81st percentile) as of Nov 14, 2026.
Activity feed

Recent activity

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

View more in app →
+3 more in the timeline. Sign up to see them
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.