CVE-2026-25212 Vulnerability Analysis & Exploit Details

CVE-2026-25212
Vulnerability Scoring

9.9
/10
Critical Risk

As a catastrophic security flaw, CVE-2026-25212 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-25212 Details

Status: Analyzed

Last updated: 🕧 21 Apr 2026, 00:33 UTC
Originally published on: 🕔 02 Apr 2026, 17:16 UTC

Time between publication and last update: 18 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-25212 Vulnerability Summary

CVE-2026-25212: 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.

Assessing the Risk of CVE-2026-25212

Access Complexity Graph

The exploitability of CVE-2026-25212 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-25212

CVE-2026-25212 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-25212, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-25212, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-25212 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-25212 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-25212 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-25212 References

External References

CWE Common Weakness Enumeration

CWE-250

CAPEC Common Attack Pattern Enumeration and Classification

  • Cross Zone Scripting CAPEC-104 An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security.
  • Expanding Control over the Operating System from the Database CAPEC-470 An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • Target Programs with Elevated Privileges CAPEC-69 This attack targets programs running with elevated privileges. The adversary tries to leverage a vulnerability in the running program and get arbitrary code to execute with elevated privileges.

Vulnerable Configurations

  • cpe:2.3:a:percona:monitoring_and_management:-:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:-:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.15.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.19.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.19.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.20.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.20.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.21.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.21.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.22.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.22.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.23.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.23.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.24.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.24.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.25.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.25.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.26.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.26.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.27.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.27.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.28.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.28.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.29.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.29.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.29.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.29.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.30.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.30.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.31.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.31.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.32.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.32.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.33.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.33.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.34.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.34.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.35.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.35.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.36.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.36.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.37.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.37.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.37.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.37.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.38.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.38.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.38.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.38.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.39.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.39.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.40.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.40.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.40.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.40.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.41.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.41.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.41.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.41.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.41.2:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.41.2:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.42.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.42.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.42.0-1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.42.0-1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.43.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.43.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.43.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.43.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.43.2:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.43.2:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.43.2-1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.43.2-1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.44.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.44.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.44.0-1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.44.0-1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:2.44.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:2.44.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.0.0-1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.0.0-1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:percona:monitoring_and_management:3.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:percona:monitoring_and_management:3.6.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-25212: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-6956 – ATutor is vulnerable to Reflected XSS in /install/install.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...
  • CVE-2026-6909 – ATutor is vulnerable to Reflected XSS in /install/upgrade.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...
  • CVE-2026-41951 – Path traversal vulnerability exists in GROWI v7.5.0 and earlier, which may allow an attacker to execute arbitrary EJS templates on the server when ...
  • CVE-2026-40636 – Dell ECS versions 3.8.1.0 through 3.8.1.7 and Dell ObjectScale versions prior to 4.3.0.0, contains a use of hard-coded credentials vulnerability. A...
  • CVE-2026-35157 – Dell ECS versions 3.8.1.0 through 3.8.1.7 and Dell ObjectScale versions prior to 4.3.0.0, contains an improper neutralization of formula elements i...