Skip to main content
Mallory
MediumVulnerability

CVE-2019-2593: Denial of Service in Oracle MySQL Server InnoDB

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
EPSS2.1%82nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Red HatFedora ProjectOracle Corporation
IdentifiersCVE-2019-2593CWE-400

CVE-2019-2593 is an unspecified vulnerability in the InnoDB component 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 crash repeatedly, resulting in complete denial of service. Exploitation has low complexity and requires no user interaction. The vulnerable function and underlying technical cause are not publicly specified in the available details.

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 through a hang or frequently repeatable crash, potentially interrupting applications that depend on the database. 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. No confidentiality or integrity impact is identified.

Mitigation

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

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

Remediation

Patch, then assume compromise.

Install vendor updates that address CVE-2019-2593. For Red Hat Software Collections on RHEL 7, apply RHSA-2019:2484; for the MySQL 8.0 module on RHEL 8, apply RHSA-2019:2511. Both updates upgrade MySQL to version 8.0.17 and automatically restart the MySQL server daemon during installation.

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-2593 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2593 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2593?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2593.
Is there a patch for CVE-2019-2593?
Install vendor updates that address CVE-2019-2593. For Red Hat Software Collections on RHEL 7, apply RHSA-2019:2484; for the MySQL 8.0 module on RHEL 8, apply RHSA-2019:2511.
What products are affected by CVE-2019-2593?
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-2593?
CVE-2019-2593 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.