Skip to main content
Mallory
MediumVulnerability

CVE-2019-2636: Denial of Service in Oracle MySQL Server Group Replication Plugin

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.4Medium · v3.1
EPSS1.7%77th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Red HatOracle Corporation
IdentifiersCVE-2019-2636CWE-400

CVE-2019-2636 is a denial-of-service vulnerability in the Group Replication Plugin of Oracle MySQL Server affecting supported versions 8.0.15 and earlier. A highly privileged attacker with network access through the MySQL protocol can cause the server to hang or repeatedly crash. Exploitation is considered difficult; the specific vulnerable function, triggering input, and underlying weakness are unspecified. The CVSS 3.0 base score is 4.4, with vector CVSS:3.0/AV:N/AC:H/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 the affected MySQL Server through a hang or frequently repeatable crashes, disrupting database availability and dependent applications. No confidentiality or integrity impact is identified, and the security scope remains unchanged.

Mitigation

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

Until patching is complete, reduce exposure by restricting MySQL protocol access to trusted systems and tightly controlling highly privileged database accounts. These measures reduce attack opportunities but do not correct the vulnerability. No vulnerability-specific workaround is identified.

Remediation

Patch, then assume compromise.

Apply a vendor update that addresses CVE-2019-2636. Red Hat Software Collections for RHEL 7 provides the fix through RHSA-2019:2484, and RHEL 8 provides it through RHSA-2019:2511; both upgrade MySQL to version 8.0.17. These updates automatically restart the MySQL server daemon, so plan for the associated service interruption.

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-2636 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2636 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2636?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2636.
Is there a patch for CVE-2019-2636?
Apply a vendor update that addresses CVE-2019-2636. Red Hat Software Collections for RHEL 7 provides the fix through RHSA-2019:2484, and RHEL 8 provides it through RHSA-2019:2511; both upgrade MySQL to version 8.0.17.
What products are affected by CVE-2019-2636?
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-2636?
CVE-2019-2636 has a CVSS v3.1 score of 4.4 (Medium) and an EPSS score of 1.7% (77th 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.