dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2026-34317

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

This is a locally exploitable denial-of-service vulnerability in MySQL Shell's Core Client component. A low-privileged attacker with logon access to the system where MySQL Shell runs can trigger the vulnerability through some unspecified interaction, causing the shell to hang or crash completely. The attack requires human interaction from a person other than the attacker.

MitigationApply the latest Oracle Critical Patch Update to obtain a patched version of MySQL Shell beyond the affected versions (8.0.45, 8.4.8, 9.6.0). In the interim, limit physical and logical access to systems running MySQL Shell and monitor for unusual shell behavior.

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. Check if MySQL Shell is installed
    Run 'which mysqlsh' or search for the mysqlsh binary in common locations like /usr/bin/mysqlsh, /opt/mysql/shell/bin/mysqlsh, or C:\Program Files\MySQL\MySQL Shell 8.0\bin\mysqlsh.exe on Windows
    Affected if MySQL Shell is found on the system
  2. Determine the installed MySQL Shell version
    Run 'mysqlsh --version' or 'mysqlsh --help' to display the version number
    Affected if The version output shows a release within the ranges 8.0.0-8.0.45, 8.4.0-8.4.8, or 9.0.0-9.6.0
  3. Identify who has physical or logical access to the MySQL Shell host
    Review system permissions, check local user accounts with logon rights, examine remote access controls (SSH, RDP), and verify console access policies
    Affected if Multiple users or untrusted parties have logon access to the system running MySQL Shell
  4. Look for signs of MySQL Shell crashes or hangs
    Review system event logs (Windows Event Viewer > Application logs), shell history files, and any core dump or crash dump directories for mysqlsh-related entries
    Affected if There are unexplained mysqlsh process terminations or hang events that coincide with multi-user activity
  5. Assess the presence of shared or interactive MySQL Shell sessions
    Check if MySQL Shell is used in shared environments, terminal services, or where multiple users interact with the same shell instance
    Affected if MySQL Shell is accessible to users who did not initiate the session, enabling the required human interaction from another person

You are affected if MySQL Shell is installed with a version between 8.0.0-8.0.45, 8.4.0-8.4.8, or 9.0.0-9.6.0 AND other users with logon access can interact with your shell sessions.

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 the latest Oracle Critical Patch Update to obtain a patched version of MySQL Shell beyond the affected versions (8.0.45, 8.4.8, 9.6.0). In the interim, limit physical and logical access to systems running MySQL Shell and monitor for unusual shell behavior.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34317 — 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-34317 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