# CVE-2025-30722: Information disclosure in MySQL Client

> A low-privileged attacker can exploit a difficult-to-exploit vulnerability in the MySQL Client to access critical data and modify some accessible data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/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:** 15 Apr 2025
- **Updated:** 3 Nov 2025
- **Also known as:** BELL-CVE-2025-30722, BIT-mariadb-2025-30722, BIT-mariadb-min-2025-30722, BIT-mysql-client-2025-30722, DEBIAN-CVE-2025-30722, ECHO-14b2-c792-e3a0, GHSA-53hw-hvww-v6v8, MINI-23h9-x456-8v6m, MINI-455h-qhpc-j6hg, MINI-8376-22rr-jp28, MINI-jmqh-5f5q-xjgq, MINI-mvj7-pwch-3x29, MINI-vc3g-whvv-hj47, UBUNTU-CVE-2025-30722

## What is CVE-2025-30722?

CVE-2025-30722 is a medium-severity vulnerability in Netapp Active Iq Unified Manager, published on 15 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the MySQL Client product of Oracle MySQL (component: Client: mysqldump).  Supported versions that are affected are 8.0.0-8.0.41, 8.4.0-8.4.4 and  9.0.0-9.2.0. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Client.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all MySQL Client accessible data as well as  unauthorized update, insert or delete access to some of MySQL Client accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N).

## Which versions are affected by CVE-2025-30722?

3 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mariadb` | Bitnami | All versions | 10.5.29, 10.6.22, 11.4.6, 11.8.2 |
| `mariadb-min` | Bitnami | All versions | 11.4.7, 11.8.2 |
| `mysql-client` | Bitnami | All versions | 10.6.22, 11.4.6, 11.8.2 |

Products: Netapp Active Iq Unified Manager, Netapp Snapcenter, Oracle Mysql Client, Oracle Mysql Cluster.

## How do I fix CVE-2025-30722?

Upgrade mariadb to a fixed version for your release line: 10.5.29, 10.6.22, 11.4.6 or 11.8.2.

## Is CVE-2025-30722 being exploited?

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

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2022-31692](https://insights.sbomify.com/CVE-2022-31692/): Spring Security authorization rules can be bypassed via forward or include dispatcher types (critical 9.8)
- [CVE-2022-2526](https://insights.sbomify.com/CVE-2022-2526/): Use after free in systemd-resolved (critical 9.8)
- [CVE-2022-22978](https://insights.sbomify.com/CVE-2022-22978/): Authorization bypass in Spring Security (critical 9.8)
- [CVE-2021-22931](https://insights.sbomify.com/CVE-2021-22931/): Code injection in Node (critical 9.8)
- [CVE-2018-2938](https://insights.sbomify.com/CVE-2018-2938/): Code injection in Java (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30722 and fix it if it is affected.

What it is: CVE-2025-30722 is a medium-severity vulnerability in Netapp Active Iq Unified Manager, published on 15 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30722 in the wild and no public exploit code.

Affected packages and fixed versions:
- mariadb (Bitnami): affected all versions; fixed in 10.5.29, 10.6.22, 11.4.6, 11.8.2
- mariadb-min (Bitnami): affected all versions; fixed in 11.4.7, 11.8.2
- mysql-client (Bitnami): affected all versions; fixed in 10.6.22, 11.4.6, 11.8.2

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-2025-30722/ (Markdown: https://insights.sbomify.com/CVE-2025-30722/index.md)
```

## Sources

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

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