All news
MediumPatch availableMedium confidenceVulnerabilities

Severity rationale: CVE-2026-34317 is rated Medium because exploitation requires local access, low privileges, and user interaction, which limits remote attack potential. However, successful exploitation can cause MySQL Shell to hang or repeatedly crash, creating a denial-of-service condition with high availability impact. The vulnerability does not currently indicate confidentiality or integrity impact, so the risk is disruptive rather than data-compromising.

CVE-2026-34317: Oracle MySQL Shell Denial-of-Service Vulnerability

Oracle · MySQL ShellCVE-2026-34317

The article covers CVE-2026-34317, a medium-severity vulnerability affecting Oracle MySQL Shell. The issue can allow a low-privileged local attacker, with required user interaction, to cause MySQL Shell to hang or repeatedly crash, resulting in a denial-of-service condition. Affected versions include MySQL Shell 8.0.0 through 8.0.45, 8.4.0 through 8.4.8, and 9.0.0 through 9.6.0. Organizations should review where MySQL Shell is installed, prioritize systems used for database administration or automation, apply the relevant Oracle security updates, and monitor for repeated mysqlsh crashes or abnormal process behavior.

By CyberBrief AI Desk May 7, 2026 2 min readLast updated May 7, 2026Reviewed May 7, 2026

Key Facts

Vendor
Oracle
Product
MySQL Shell
CVE
CVE-2026-34317
CVSS
5
Exploitation
No exploitation observed
Affected versions
MySQL Shell versions 8.0.0 through 8.0.45, MySQL Shell versions 8.4.0 through 8.4.8, MySQL Shell versions 9.0.0 through 9.6.0
Fixed versions
https://www.oracle.com/security-alerts/cpuapr2026.html

Summary

CVE-2026-34317 is a medium-severity denial-of-service vulnerability in Oracle MySQL Shell. It affects the Shell: Core Client component and can allow a low-privileged attacker with local logon access to disrupt MySQL Shell by causing the application to hang or repeatedly crash. NVD lists Oracle as the source and identifies the affected product as Oracle MySQL Shell.

What happened

Oracle disclosed CVE-2026-34317 as part of its April 2026 Critical Patch Update. Oracle’s MySQL Community Edition advisory lists CVE-2026-34317 under MySQL Shell, specifically the Shell: Core Client component, with a CVSS score of 5.0 and the affected version ranges listed above.

Why it matters

The primary risk is operational disruption. MySQL Shell is commonly used by database administrators and developers to manage MySQL environments. If an attacker with local access can trigger repeated crashes, database administration workflows may be interrupted.

This vulnerability does not provide confidentiality or integrity impact according to the CVSS vector. In plain English, the public scoring does not indicate data theft or data modification as expected outcomes. The documented impact is availability loss.

Affected systems

Organizations should review systems running Oracle MySQL Shell versions:

8.0.0 through 8.0.45
8.4.0 through 8.4.8
9.0.0 through 9.6.0

Oracle’s MySQL Community Edition advisory lists these version ranges as affected for MySQL Shell.

Recommended actions

  1. Upgrade MySQL Shell: Apply the relevant Oracle MySQL updates from the April 2026 Critical Patch Update. Oracle’s advisory identifies CVE-2026-34317 as part of the April 2026 MySQL security update set.
  2. Limit Local Access: Because exploitation requires local logon access, restrict access to systems where MySQL Shell is installed. Use least privilege and remove unnecessary interactive access.
  3. Prioritize Administrative Systems: Focus first on database administration hosts, bastion systems, automation runners, and developer systems that interact with production MySQL environments.
  4. Monitor for Crashes: Add monitoring for repeated MySQL Shell crashes, hangs, or abnormal process exits. A denial-of-service issue can be easy to overlook if it looks like “just another broken admin tool.” Tiny gremlin, big interruption.

Technical details

The vulnerability is associated with CWE-404, Improper Resource Shutdown or Release. NVD’s CVSS vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H, which means the attack is local, low complexity, requires low privileges, requires user interaction, has unchanged scope, and affects availability only.

Ubuntu also rates the issue as medium priority with a CVSS 3 score of 5.0 and the same local attack vector, low privileges requirement, required user interaction, and high availability impact.

Detection & hunting

Review systems for installed MySQL Shell versions.
Monitor for repeated mysqlsh crashes or hangs.
Review local user activity on systems where MySQL Shell is used.
Check endpoint and system logs for abnormal MySQL Shell termination events.
Validate whether MySQL Shell is installed on administrative jump boxes, database management hosts, developer workstations, and automation servers.

Recommended actions

P1

Patch/Remediate

  • Apply the relevant Oracle MySQL updates from the April 2026 Critical Patch Update.
  • Upgrade Oracle MySQL Shell on affected systems running versions 8.0.0 through 8.0.45, 8.4.0 through 8.4.8, or 9.0.0 through 9.6.0.
  • Confirm the installed MySQL Shell version after patching using mysqlsh --version.
P2

Asset Review

  • Inventory systems to identify where Oracle MySQL Shell is installed.
  • Prioritize database administration hosts, bastion systems, automation runners, developer workstations, and production support systems.
P2

Access Control

  • Restrict local logon access to systems where Oracle MySQL Shell is installed.
  • Apply least privilege for users who require MySQL Shell access.
  • Remove unnecessary interactive access from non-administrative users.
P3

Detection/Monitoring

  • Monitor for repeated mysqlsh crashes, hangs, or abnormal process exits.
  • Review endpoint and system logs for unusual local user activity involving MySQL Shell.
  • Create alerts for frequent MySQL Shell termination events on administrative or production support systems.
P3

Monitor/Track

  • Track Oracle security advisories for updates related to CVE-2026-34317.
  • Monitor NVD, Ubuntu security notes, and vendor advisories for changes in severity, exploit status, or affected versions.
0

Sources

ShareXLinkedIn

Disclaimer: CyberBrief HQ articles are for informational purposes only and do not constitute security advice for any specific environment. Always validate guidance against your own controls and vendor advisories before acting.