Skip to main content
Mallory
MediumVulnerability

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

Published Oct 16, 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.6%85th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
NetAppFedora ProjectOracle CorporationCanonical
IdentifiersCVE-2019-2968CWE-400

CVE-2019-2968 is a denial-of-service vulnerability in the InnoDB component of Oracle MySQL Server, affecting supported versions 8.0.17 and earlier. A highly privileged attacker with network access through multiple protocols can cause the server to hang or repeatedly crash. Exploitation has low complexity and requires no user interaction. The underlying defect and vulnerable function are unspecified. 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 cause a complete denial of service of MySQL Server through a hang or frequently repeatable crash, disrupting database availability. The assessed impact is high for availability, with no confidentiality or integrity impact and no change in security scope.

Mitigation

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

No vulnerability-specific workaround is documented. Pending patching, restrict network access to MySQL to trusted systems and minimize access to highly privileged database accounts as defense-in-depth measures.

Remediation

Patch, then assume compromise.

Install a vendor-fixed MySQL package or upgrade the affected MySQL 8.0 installation to version 8.0.18 or a later supported release. Ubuntu provided MySQL 8.0.18 for Ubuntu 19.10 through USN-4195-1. Red Hat supplied MySQL 8.0.21 through RHSA-2020:3518, RHSA-2020:3732, RHSA-2020:3755, and RHSA-2020:3757 for applicable product streams; installation automatically restarts the MySQL server. For affected Red Hat container deployments, update the base image and rebuild dependent images. Unity Linux deployments should install the updated mysql package identified by UTSA-2026-153631.

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
CanonicalUbuntu Linuxoperating_system
Fedora ProjectFedoraoperating_system
NetAppActiveiq Unified Managerapplication
NetAppOncommand Insightapplication
NetAppOncommand Workflow Automationapplication
NetAppSnapcenterapplication
Oracle CorporationMysqlapplication
FAQ

Frequently asked questions

Is CVE-2019-2968 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2968 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2968?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2968.
Is there a patch for CVE-2019-2968?
Install a vendor-fixed MySQL package or upgrade the affected MySQL 8.0 installation to version 8.0.18 or a later supported release. Ubuntu provided MySQL 8.0.18 for Ubuntu 19.10 through USN-4195-1.
What products are affected by CVE-2019-2968?
Oracle Corporation Mysql, NetApp Activeiq Unified Manager, Fedora Project Fedora, NetApp Oncommand Insight, NetApp Oncommand Workflow Automation, and 2 more.
How severe is CVE-2019-2968?
CVE-2019-2968 has a CVSS v3.1 score of 4.9 (Medium) and an EPSS score of 2.6% (85th percentile) as of Nov 14, 2026.
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.