dbcve.org
Monitoring And ManagementApplication · Percona

CVE-2026-25212

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 3.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Percona PMM before version 3.7 contains an internal database user that retains specific superuser privileges. An authenticated attacker with pmm-admin rights can exploit the 'Add data source' feature to escape the database context and execute arbitrary shell commands on the underlying operating system, achieving full system compromise.

MitigationUpgrade Percona PMM to version 3.7 or later, which removes the excessive superuser privileges from the internal database user. If immediate upgrade is not feasible, restrict pmm-admin access to trusted personnel and monitor for suspicious datasource configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Monitoring And ManagementApplication
Affected:< 3.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify PMM version
    Run 'pmm-admin --version' or check the PMM server UI dashboard for the installed version number
    Affected if The installed version is lower than 3.7.0 (e.g., 3.6.x, 3.5.x, etc.)
  2. Verify pmm-admin user existence
    List users with pmm-admin roles via 'pmm-admin list' or through the PMM user management interface
    Affected if Any pmm-admin user accounts exist in the system
  3. Confirm Add data source feature access
    Check if the Add data source functionality is available in the PMM interface under Configuration or Data Sources settings
    Affected if The Add data source feature is enabled or accessible to pmm-admin users
  4. Inspect internal database configuration
    Review the PMM internal database (PostgreSQL/MySQL) user privileges, specifically looking for database users with superuser or elevated privileges beyond sandbox restrictions
    Affected if An internal database user has superuser privileges retained beyond necessary sandbox boundaries

You are affected if PMM version is below 3.7.0 AND pmm-admin users exist with access to the Add data source feature, as this combination enables the privilege escalation and OS command execution path.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.7.0 or later
Fixed in 3.7.0
Interim mitigation

Upgrade Percona PMM to version 3.7 or later, which removes the excessive superuser privileges from the internal database user. If immediate upgrade is not feasible, restrict pmm-admin access to trusted personnel and monitor for suspicious datasource configurations.

Recommended fix High confidence

Percona PMM 3.7.0 or later

  1. 1. Backup the current PMM configuration and data according to Percona documentation.
  2. 2. Stop the PMM server instance.
  3. 3. Upgrade PMM to version 3.7.0 or later using the official upgrade procedure (e.g., pmm-server docker upgrade or package manager update).
  4. 4. Verify the upgrade completed successfully by checking the PMM version.
  5. 5. Confirm the internal database user privileges have been properly restricted by reviewing PMM 3.7.0 release notes or documentation.
  6. 6. Restart the PMM services.
  7. 7. Validate that the 'Add data source' feature still functions correctly for legitimate monitoring purposes.
Caveat Review PMM 3.7.0 release notes for any deprecated features or configuration changes that may affect your monitoring setup

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Monitoring And Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data