# CVE-2025-30706: Privilege escalation in MySQL Connectors

> A low-privileged attacker can compromise MySQL Connectors via network access, leading to full takeover of the connector component.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 26 Feb 2026
- **Also known as:** GHSA-mxpq-3mg3-vqx7, SUSE-SU-2025:21144-1, UBUNTU-CVE-2025-30706, openSUSE-SU-2025:15026-1, openSUSE-SU-2025:20089-1

## What is CVE-2025-30706?

CVE-2025-30706 is a high-severity vulnerability in Oracle Corporation MySQL Connectors, 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 Connectors product of Oracle MySQL (component: Connector/J).  Supported versions that are affected are 9.0.0-9.2.0. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors.  Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mysql-connector-java` | SUSE:Linux Enterprise Server 16.0 | All versions | 9.3.0-160000.1.1 |
| `mysql-connector-java` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 9.3.0-160000.1.1 |
| `mysql-connector-java` | openSUSE:Leap 16.0 | All versions | 9.3.0-160000.1.1 |
| `mysql-connector-java` | openSUSE:Tumbleweed | All versions | 9.3.0-1.1 |

Products: Oracle Mysql Connector\/J.

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

Apply the vendor's patch.

## Is CVE-2025-30706 being exploited?

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

## Other vulnerabilities in Oracle Corporation MySQL Connectors

- [CVE-2026-60586](https://insights.sbomify.com/CVE-2026-60586/): Missing authorization in MySQL Connectors (high 7.7)
- [CVE-2026-60623](https://insights.sbomify.com/CVE-2026-60623/): Missing authorization in MySQL Connectors (high 7.1)
- [CVE-2026-60624](https://insights.sbomify.com/CVE-2026-60624/): Denial of service in MySQL Connectors (medium 6.5)
- [CVE-2026-61082](https://insights.sbomify.com/CVE-2026-61082/): Open redirect in MySQL Connectors (medium 6.5)
- [CVE-2019-2692](https://insights.sbomify.com/CVE-2019-2692/): Privilege escalation in mysql-connector-jav (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30706 is a high-severity vulnerability in Oracle Corporation MySQL Connectors, 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-30706 in the wild and no public exploit code.

Affected product: Oracle Corporation MySQL Connectors. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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