CVE-2026-34267: Oracle MySQL Server · Uncontrolled Resource Consumption
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle CorporationMySQL Server | Affected
| Fixed in– |
Mavencom.oracle/mysql-serverpkg:maven/com.oracle/mysql-serverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Oracle has released security patches for this vulnerability in the April 2026 Critical Patch Update. Users running affected versions of MySQL Server (8.0.0 through 8.0.45) should apply the April 2026 Critical Patch Update without delay to remediate this vulnerability. No other mitigation or workaround is indicated by the vendor advisory.
Description
CVE-2026-34267 is a vulnerability in Oracle MySQL Server versions 8.0.0 through 8.0.45 affecting the Server Optimizer component. It allows a high privileged attacker with network access via multiple protocols to cause a hang or repeated crash of the MySQL Server, resulting in a denial of service (DoS). The vulnerability has a CVSS 3.1 base score of 4.9, indicating a medium severity focused on availability impact. Oracle has included this vulnerability in its April 2026 Critical Patch Update, which provides security patches addressing this and other vulnerabilities.