CVE-2026-22017
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.0-8.0.45, 8.4.0-8.4.8 and 9.0.0-9.6.0. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA denial of service vulnerability exists in the MySQL Server Optimizer component. Low-privileged attackers with network access can exploit this flaw to cause the MySQL server to hang or crash repeatedly, resulting in complete service unavailability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 8.0.0, <= 8.0.45>= 8.4.0, <= 8.4.8>= 9.0.0, <= 9.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed MySQL versionRun `mysql --version` on the server command line, or connect to MySQL and execute `SELECT VERSION();`Affected if The version falls within 8.0.0-8.0.45, 8.4.0-8.4.8, or 9.0.0-9.6.0
-
Confirm network interface bindingCheck the MySQL configuration file (my.cnf or my.ini) for the `bind-address` setting, or run `SHOW VARIABLES LIKE 'bind_address';`Affected if MySQL is bound to a non-localhost address (0.0.0.0 or a specific IP) allowing remote connections
-
Verify port accessibilityCheck if port 3306 (or the configured MySQL port) is open externally using `netstat -tuln | grep <port>` or a port scanner from a remote hostAffected if The MySQL port is reachable from untrusted networks
-
Review user privilege grantsExecute `SELECT user, host, plugin FROM mysql.user;` to see which users have network access, especially non-admin accountsAffected if Low-privileged users with network access (non-localhost hosts) exist in the user table
You are affected if your MySQL version is within the affected ranges AND the server accepts network connections accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply Oracle's critical patch updates for the affected MySQL versions (8.0.46+, 8.4.9+, 9.0.1+) or upgrade to a patched release. Prioritize deployment in staging and test for regression issues before production rollout.
MySQL 8.0.46+ / 8.4.9+ / latest 9.x stable release
- 1. Identify the currently installed MySQL Server version using: SELECT VERSION();
- 2. For MySQL 8.0.x users: Upgrade to MySQL 8.0.46 or later
- 3. For MySQL 8.4.x users: Upgrade to MySQL 8.4.9 or later
- 4. For MySQL 9.0.x users: Upgrade to the latest 9.x release available from Oracle
- 5. Download the updated MySQL Server from the official Oracle website: https://www.oracle.com/downloads/
- 6. Follow Oracle's standard upgrade documentation for your version line
- 7. Test the upgrade in a non-production environment before deploying to production
- 8. After upgrade, verify the version with SELECT VERSION(); to confirm the patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data