Skip to main content
Mallory
MediumVulnerability

CVE-2019-2628: 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 days1 mention · peak 1 in a dayToday
CVSS4.9Medium · v3.1
EPSS2.8%87th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Red HatMariaDBOracle CorporationOpensuseCanonical
IdentifiersCVE-2019-2628CWE-400

CVE-2019-2628 is an unspecified vulnerability in the InnoDB component of Oracle MySQL Server affecting the 5.7 branch through 5.7.25 and the 8.0 branch 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 specific vulnerable function and underlying weakness are not publicly specified. 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 loss of MySQL Server availability through a hang or frequently repeatable crash, disrupting database access and dependent applications. The published CVSS assessment identifies no confidentiality or integrity impact and no scope change.

Mitigation

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

Restrict MySQL network access to trusted clients and networks, and limit high-privilege database accounts to only necessary users and services. Monitor for unexpected database daemon hangs or repeated restarts. These measures reduce exposure but do not replace applying the security update.

Remediation

Patch, then assume compromise.

Apply the vendor security update appropriate to the installed product and distribution. Ubuntu addressed the vulnerability in MySQL 5.7.26 through USN-3957-1. Red Hat supplied fixes in MySQL 8.0.17 through RHSA-2019:2484 and RHSA-2019:2511. Corresponding MariaDB fixes include version 10.3.17 for Ubuntu 19.04 and RHEL 8, with other Software Collections and SAP channels receiving separate updates. Unity Linux deployments should install the updated mysql package identified by UTSA-2026-153416. Relevant Red Hat updates automatically restart the database server after 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
CanonicalUbuntu Linuxoperating_system
MariaDBMariadbapplication
OpensuseOpensuse Leapoperating_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
FAQ

Frequently asked questions

Is CVE-2019-2628 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2628 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2628?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2628.
Is there a patch for CVE-2019-2628?
Apply the vendor security update appropriate to the installed product and distribution. Ubuntu addressed the vulnerability in MySQL 5.7.26 through USN-3957-1.
What products are affected by CVE-2019-2628?
Oracle Corporation Mysql, Red Hat Enterprise Linux Eus, Red Hat Enterprise Linux Server Aus, Red Hat Enterprise Linux Server Tus, Mariadb, and 3 more.
How severe is CVE-2019-2628?
CVE-2019-2628 has a CVSS v3.1 score of 4.9 (Medium) and an EPSS score of 2.8% (87th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

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

View more in app →
+8 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.