CVE-2026-34308
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: JSON). 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 MySQL Server's JSON component. Low-privileged attackers with network access can exploit this to cause MySQL Server to hang or experience repeatable crashes, resulting in complete availability loss.
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.
-
Confirm MySQL Server is installedRun 'mysql --version' or check the installed MySQL packages using the system's package manager (e.g., 'dpkg -l | grep mysql', 'rpm -qa | grep mysql', or 'mysql_install_db --version')Affected if MySQL Server is present on the system
-
Retrieve the running MySQL Server versionConnect to MySQL and run 'SELECT VERSION();' or check the mysqld binary version with 'mysqld --version'Affected if The version falls within any of these ranges: 8.0.0 through 8.0.45, 8.4.0 through 8.4.8, or 9.0.0 through 9.6.0
-
Verify network access to MySQLCheck if MySQL is listening on a network port by reviewing my.cnf for 'bind-address' settings, or use 'netstat -tlnp | grep 3306' or 'ss -tlnp | grep 3306' to see if port 3306 (or configured port) is listening on an IP other than localhostAffected if MySQL accepts remote connections and is reachable over the network (the attacker needs network access)
-
Confirm low-privileged user access existsReview user privileges in MySQL by running 'SELECT user, host FROM mysql.user;' to identify accounts with limited privileges that could be exploitedAffected if There are non-admin, network-accessible user accounts in MySQL (the flaw is exploitable by low-privileged attackers)
If MySQL Server is running a version between 8.0.0-8.0.45, 8.4.0-8.4.8, or 9.0.0-9.6.0 AND the server is accessible over the network to low-privileged users, the environment is affected by this CVE.
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 · scopedUpgrade MySQL Server to a version beyond 8.0.45, 8.4.8, or 9.6.0 (depending on the major branch in use) to obtain the patched version.
MySQL 8.0.46+ / 8.4.9+ / 9.0.1+ (upgrade to the latest patch release in your major version branch)
- 1. Identify the currently installed MySQL Server version using: SELECT VERSION();
- 2. Based on your major version (8.0.x, 8.4.x, or 9.x), plan upgrade to the next available patch release that exceeds the vulnerable version range
- 3. For MySQL 8.0.x users: upgrade to MySQL 8.0.46 or later
- 4. For MySQL 8.4.x users: upgrade to MySQL 8.4.9 or later
- 5. For MySQL 9.x users: upgrade to MySQL 9.0.1 or later
- 6. Before upgrading in production, test the upgrade in a staging environment to verify application compatibility
- 7. Take a complete backup of all databases before performing the upgrade
- 8. Review MySQL upgrade documentation for your specific version jump at https://dev.mysql.com/doc/refman/
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34308 — 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-34308 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