# CVE-2026-46871: Missing authorization in MySQL Shell

> A low-privileged attacker can exploit a missing authorization flaw in MySQL Shell for VS Code to gain unauthorized access to critical data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** BIT-mysql-shell-2026-46871, GHSA-wmrj-pjxx-fh6x

## What is CVE-2026-46871?

CVE-2026-46871 is a medium-severity missing authorization vulnerability in Oracle Corporation MySQL Shell, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 multiple protocols to compromise MySQL Shell.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all MySQL Shell accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-46871?

1 open source package ship an affected version, including mysql-shell. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mysql-shell` | Bitnami | From 2026.2.0 | 2026.5.0 |

Products: Oracle Mysql Shell.

## How do I fix CVE-2026-46871?

Upgrade mysql-shell to 2026.5.0 or later.

## Is CVE-2026-46871 being exploited?

There is no known exploitation of CVE-2026-46871 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Corporation MySQL Shell

- [CVE-2026-46850](https://insights.sbomify.com/CVE-2026-46850/): Code injection in MySQL Shell (critical 9.9)
- [CVE-2026-46870](https://insights.sbomify.com/CVE-2026-46870/): Auth bypass in MySQL Shell (high 8.5)
- [CVE-2026-46869](https://insights.sbomify.com/CVE-2026-46869/): Cross-site request forgery in MySQL Shell (medium 6.5)
- [CVE-2022-21555](https://insights.sbomify.com/CVE-2022-21555/): Missing authorization in MySQL Server (medium 4.2)
- [CVE-2022-21535](https://insights.sbomify.com/CVE-2022-21535/): Denial of service in MySQL Server (low 2.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46871 and fix it if it is affected.

What it is: CVE-2026-46871 is a medium-severity missing authorization vulnerability in Oracle Corporation MySQL Shell, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46871 in the wild and no public exploit code.

Affected packages and fixed versions:
- mysql-shell (Bitnami): affected from 2026.2.0; fixed in 2026.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46871/ (Markdown: https://insights.sbomify.com/CVE-2026-46871/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46871
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46871
- OSV: https://osv.dev/vulnerability/CVE-2026-46871

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46871/
Summaries are generated and may contain mistakes; the official description above is the record.
