# CVE-2026-25212: Privilege escalation in n/a

> Attackers with pmm-admin rights can execute shell commands on the OS by abusing the Add data source feature due to excessive database privileges.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** No
- **Published:** 2 Apr 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-hm6f-x2ww-p497

## What is CVE-2026-25212?

CVE-2026-25212 is a critical vulnerability in n/a, published on 2 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Percona PMM before 3.7. Because an internal database user retains specific superuser privileges, an attacker with pmm-admin rights can abuse the "Add data source" feature to break out of the database context and execute shell commands on the underlying operating system.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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

It affects 1 product.


Products: Percona Monitoring and Management.

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

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

## Is CVE-2026-25212 being exploited?

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

Public exploit code:

- POC for CVE-2026-25212 (github_poc): https://github.com/5170Temp/CVE-2026-25212

## Other vulnerabilities in n/a

- [CVE-2023-34409](https://insights.sbomify.com/CVE-2023-34409/): Path traversal in n/a (critical 9.8)
- [CVE-2020-7920](https://insights.sbomify.com/CVE-2020-7920/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25212 is a critical vulnerability in n/a, published on 2 Apr 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-25212 in the wild and no public exploit code.

Affected product: n/a. 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-2026-25212/ (Markdown: https://insights.sbomify.com/CVE-2026-25212/index.md)
```

## Sources

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

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