# CVE-2026-34318: Information disclosure in MySQL Shell

> A high-privileged attacker can exploit a difficult-to-exploit vulnerability in MySQL Shell to gain unauthorized access to critical data.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** BIT-mysql-shell-2026-34318, GHSA-m58j-v3j6-3hqq, OESA-2026-2256, UBUNTU-CVE-2026-34318

## What is CVE-2026-34318?

CVE-2026-34318 is a medium-severity vulnerability in Oracle Mysql, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols 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  unauthorized access to critical data or complete access to all MySQL Shell accessible data. CVSS 3.1 Base Score 5.8 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mysql-shell` | Bitnami | All versions | 8.0.46, 8.4.9, 9.7.0 |

Products: Oracle Mysql.

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

Upgrade mysql-shell to a fixed version for your release line: 8.0.46, 8.4.9 or 9.7.0.

## Is CVE-2026-34318 being exploited?

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

## Other vulnerabilities in Oracle Mysql

- [CVE-2016-0639](https://insights.sbomify.com/CVE-2016-0639/): Auth bypass in n/a (critical 9.8)
- [CVE-2003-0150](https://insights.sbomify.com/CVE-2003-0150/): Privilege escalation in n/a (critical 9.0)
- [CVE-2005-2572](https://insights.sbomify.com/CVE-2005-2572/): Denial of service in n/a (high 8.5)
- [CVE-2020-14878](https://insights.sbomify.com/CVE-2020-14878/): Auth bypass in MySQL Server (high 8.0)
- [CVE-2002-0969](https://insights.sbomify.com/CVE-2002-0969/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34318 is a medium-severity vulnerability in Oracle Mysql, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34318 in the wild and no public exploit code.

Affected packages and fixed versions:
- mysql-shell (Bitnami): affected all versions; fixed in 8.0.46, 8.4.9, 9.7.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-34318/ (Markdown: https://insights.sbomify.com/CVE-2026-34318/index.md)
```

## Sources

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

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