dbcve.org
Mysql ShellDatabase / datastore · Oracle

CVE-2026-46850

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 for VS Code). The supported version that is affected is 2026.2.0+9.6.1. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise MySQL Shell. While the vulnerability is in MySQL Shell, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of MySQL Shell. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 confidence

A critical vulnerability in MySQL Shell for VS Code allows low-privileged attackers with network access via HTTP to achieve complete system takeover. The vulnerability affects version 2026.2.0+9.6.1 and exhibits a scope change, potentially impacting additional products beyond MySQL Shell. The CVSS 9.9 score indicates trivial exploitability with total compromise of confidentiality, integrity, and availability.

MitigationApply vendor-supplied patches or updates for MySQL Shell for VS Code as soon as available. Until patched, restrict network access to the affected component and monitor for suspicious HTTP traffic.

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
Mysql ShellDatabase / datastore
Affected:= 2026.2.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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. Identify MySQL Shell installation
    Check for MySQL Shell installation by running 'mysqlsh --version' or 'mysqlsh --help' in command line, or check installed packages via system package manager (dpkg -l mysql-shell, rpm -qa mysql-shell, or similar)
    Affected if MySQL Shell version 2026.2.0 is installed and no patch has been applied
  2. Verify installed version matches vulnerable release
    Compare the output from 'mysqlsh --version' or package query against the affected version 2026.2.0 (note: also affects version 9.6.1 per summary indicating 2026.2.0+9.6.1 range)
    Affected if Installed version is 2026.2.0 or falls within the 9.6.1+ range without vendor patch
  3. Check for HTTP listener configuration
    Examine MySQL Shell configuration files (check ~/.mysqlsh/ or /etc/mysqlsh/ directories) and look for http or listener settings in config files, or attempt to connect to local HTTP port (default 33060) if MySQL Shell has REST API enabled
    Affected if HTTP server/listener is enabled in MySQL Shell configuration, allowing network-accessible HTTP interface
  4. Confirm network exposure
    Verify if MySQL Shell HTTP service is bound to network-accessible interface (0.0.0.0) rather than localhost only, by checking config or using 'netstat -tlnp' or 'ss -tlnp' to list listening ports
    Affected if MySQL Shell HTTP service is listening on non-localhost interface (0.0.0.0) and accessible over network

User is affected if MySQL Shell version 2026.2.0 (or 9.6.1+) is installed with HTTP interface enabled and network-accessible, allowing remote attackers HTTP access to the service.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or updates for MySQL Shell for VS Code as soon as available. Until patched, restrict network access to the affected component and monitor for suspicious HTTP traffic.

Fix this in Mysql Shell Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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