dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2026-34319

MEDIUM · 5.0 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to after 9.6.0 or later.
See remediation →
50/100
Remediation priority · Moderate

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 · unedited
Vulnerability in the MySQL Shell product of Oracle MySQL (component: Shell: Core Client). 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 logon to the infrastructure where MySQL Shell executes to compromise MySQL Shell. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Shell. CVSS 3.1 Base Score 5.0 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 · high confidence

Local denial-of-service vulnerability in MySQL Shell's Core Client component. An attacker with low privileges and local system access, combined with human interaction from another user, can cause MySQL Shell to hang or crash completely. The attack vector is local (AV:L), requires low privileges (PR:L), and demands user interaction (UI:R).

MitigationApply Oracle's security patch for this vulnerability when available, and restrict local access to systems running MySQL Shell to minimize attack surface.

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
MySQLDatabase / datastore
Affected:>= 8.0.0, <= 8.0.45>= 8.4.0, <= 8.4.8>= 9.0.0, <= 9.6.0

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify MySQL Shell is installed
    Check for the mysqlsh binary on the system. Common locations: which mysqlsh (Linux/macOS) or where mysqlsh (Windows). Also check common installation paths like /opt/mysql-shell/bin/mysqlsh or C:\Program Files\MySQL\MySQL Shell\bin\mysqlsh.exe
    Affected if MySQL Shell is not installed on the system - the vulnerability does not apply
  2. Determine installed MySQL Shell version
    Run 'mysqlsh --version' or 'mysqlsh --api-version' from the command line. The output will display the version number (for example: 8.0.35 or 9.1.0)
    Affected if Command fails or mysqlsh is not found - proceed to check 1
  3. Compare version against affected ranges
    Analyze the version number from step 2 against these vulnerable ranges: 8.0.0 through 8.0.45 inclusive, 8.4.0 through 8.4.8 inclusive, or 9.0.0 through 9.6.0 inclusive. Any version matching these ranges is affected
    Affected if Installed version falls within any of the listed vulnerable ranges (8.0.x where x<=45, 8.4.x where x<=8, or 9.x.y where x<=6)
  4. Assess local access and user interaction exposure
    Review system access controls and determine if low-privileged users can access the system locally and if multiple users interact with MySQL Shell. Check if MySQL Shell is used in shared or multi-user environments
    Affected if System allows low-privileged local users to access MySQL Shell and multiple users interact with the system, increasing the likelihood of exploitation

A system is affected if MySQL Shell is installed AND its version falls within 8.0.0-8.0.45, 8.4.0-8.4.8, or 9.0.0-9.6.0 AND low-privileged local users can access the system where human interaction from another user is possible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 9.6.0
Interim mitigation

Apply Oracle's security patch for this vulnerability when available, and restrict local access to systems running MySQL Shell to minimize attack surface.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34319 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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