CVE-2026-22004: 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: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, 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– |
AI-suggested
Oracle has released a Critical Patch Update in April 2026 that includes fixes for this vulnerability. Customers should apply the April 2026 Critical Patch Update promptly to remediate this issue. The vendor advisory at https://www.oracle.com/security-alerts/cpuapr2026.html provides detailed patch availability and installation instructions. No alternative mitigations or temporary fixes are specified. Staying on actively supported versions and applying Oracle's cumulative security patches without delay is strongly recommended.
Description
CVE-2026-22004 is a vulnerability in Oracle MySQL Server affecting versions 8.0.0 through 8.0.45, 8.4.0 through 8.4.8, and 9.0.