# CVE-2025-8107: Privilege escalation in OceanBase Server

> A malicious user with specific privileges can escalate to SYS-level access in OceanBase Oracle mode tenants via crafted commands.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2025
- **Updated:** 31 Jul 2025
- **Also known as:** GHSA-vqq6-5vrp-4ffj

## What is CVE-2025-8107?

CVE-2025-8107 is a medium-severity vulnerability in OB OceanBase Server, published on 24 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OceanBase's Oracle tenant mode, a malicious user with specific privileges can achieve privilege escalation to SYS-level access by executing carefully crafted commands.

This vulnerability only affects OceanBase tenants in Oracle mode. Tenants in MySQL mode are unaffected.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-269 (Improper Privilege Management)

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


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

No fix has been published for CVE-2025-8107 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8107 is a medium-severity vulnerability in OB OceanBase Server, published on 24 Jul 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-8107 in the wild and no public exploit code.

Affected product: OB OceanBase Server. 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-8107/ (Markdown: https://insights.sbomify.com/CVE-2025-8107/index.md)
```

## Sources

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

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