Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local shell on Guardium appliance
-
ExploitAccess pkcrypto passkey component
-
ExecutionRecover root password via hard-coded recovery key
-
ImpactAuthenticate as root with full control
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK
2 techniques across 2 tactics: Persistence, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access to an IBM Guardium Data Protection 12.2 appliance with at least low-level privileges (PR:L), plus the presence of the vulnerable pkcrypto passkey component that ships with the hard-coded recovery key. The decisive condition is the hard-coded recovery key embedded in pkcrypto combined with weak cryptographic protection of the root password - any actor who can reach that component locally and knows or derives the key can recover root. Limiting factors: there is NO network attack path (AV:L), no unauthenticated remote exploitation is possible, and the attacker must first establish a local presence on the appliance; no user interaction is required (UI:N). These constraints substantially narrow realistic exploitation to insiders or attackers who have already breached the appliance via another vector. |
| Impact | This is a genuinely serious technical flaw but not an emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8 HIGH) and the SSVC 'Technical Impact: total' rating agree that successful exploitation yields complete compromise - root on the Guardium appliance via a hard-coded recovery key (CWE-798). However, every exploitation signal points to this being a lower-urgency item rather than a mass-exploitation threat: the attack vector is local (AV:L), not network, so the attacker must already have a foothold on the appliance with at least low privileges (PR:L); EPSS is only 0.11% (1st percentile); SSVC marks Exploitation as 'none' and Automatable as 'no'; the CVE is not in CISA KEV; and no public exploit code was identified. These signals are consistent with each other - there is no CVSS/EPSS/KEV conflict here. The low EPSS and local-only vector are both explained by the requirement for prior local access, which inherently limits scale. Net assessment: a high-impact local privilege-escalation issue that matters a great deal on any Guardium host an attacker can already touch (it defeats the appliance's root-account protection), but it is not a widespread-exploitation priority. Patch promptly as part of normal maintenance; it is not a drop-everything network-exposed RCE. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged local shell on an IBM Guardium Data Protection 12.2 appliance invokes the weak pkcrypto passkey logic and uses the embedded hard-coded recovery key to reconstruct or reset the root password, then logs in as root. No public exploit code was identified at time of analysis, so this would require the attacker to reverse-engineer or already know the hard-coded key. Because the attack is local (AV:L) with low complexity (AC:L), it is straightforward once appliance access is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 09, 2026
Local privilege escalation in IBM Guardium Data Protection 12.2 allows an attacker who already holds low-privilege local access on the appliance to recover the root password through the pkcrypto passkey component and thereby obtain full root control, because that component combines weak cryptographic protection with a hard-coded recovery key (CWE-798). The exposure is confined to a local attack path (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning no network or unauthenticated remote vector exists and the attacker must first establish a foothold on the appliance - realistically an insider or someone who has already compromised the host by other means. There is no public exploit identified at time of analysis, CISA SSVC rates exploitation as none and the flaw as non-automatable while assigning total technical impact, and EPSS is 0.11% (1st percentile), so this is a serious but not urgent technical issue.
Earlier versions of this analysis (1)
Local privilege escalation in IBM Guardium Data Protection 12.2 allows an attacker who already has a foothold on the appliance to recover the root password and obtain full root privileges. The pkcrypto passkey component relies on weak cryptographic protection combined with a hard-coded recovery key, so a local user needs no credentials and no user interaction to exploit it (CVSS:3.1/AV:L/AC:L/PR:N/UI:N, base 8.4, CWE-798). Exploitation is constrained by the local attack vector - network reachability alone is insufficient and the attacker must already hold a local account or console/shell access on an affected 12.2 host - and no public exploit code has been identified at time of analysis; a vendor patch is available.
RemediationAI
Patch status per the provided data is 'Patch available per vendor advisory' - no exact fixed build number is given in the source material, so the IBM support page at https://www.ibm.com/support/pages/node/7288035 should be consulted for the precise firmware or fix-pack level and applied to all Guardium Data Protection 12.2 appliances; confirm the applied build against that advisory rather than assuming a generic 12.2.x update resolves the hard-coded key, since the flaw requires replacement of the affected pkcrypto component, not just a version bump. Because the attack prerequisite is only low-privilege local access, tightening local access is an effective compensating control while patching is staged: restrict interactive shell and SSH access on the appliance to the smallest possible set of administrators, remove unnecessary local accounts and trim sudo rights, and audit for any account that could invoke pkcrypto - the trade-off is reduced operational flexibility for DBAs and support staff who currently rely on local troubleshooting. Rotating the root password is worth doing but is not a fix on its own, since the hard-coded recovery key remains and the password can be recovered again; likewise, deleting or heavily locking down pkcrypto binaries and its key material may break Guardium's own credential-recovery and backup-restore workflows, so any such change must be validated against the vendor's supported configuration. Lastly, monitor appliance logs for unexpected privilege escalation or reads of pkcrypto paths, and immediately rotate root and any appliance-managed database credentials if local compromise is suspected.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The defect sits in the pkcrypto passkey component of IBM Guardium Data Protection 12.2, which is responsible for protecting and recovering credential material on the appliance. Per CWE-798 (Use of Hard-coded Credentials), the component ships with a recovery key that is fixed in the product rather than generated per deployment, and the cryptographic safeguards wrapping the root password are weak enough that possession or derivation of that key yields the root credential in recoverable form. This is fundamentally a secrets-management and key-lifecycle failure rather than a memory-safety or injection bug: the trust anchor itself is static and shared across installations, so the confidentiality of the appliance root account depends on something an attacker with local read access can obtain. The CPE entry cpe:2.3:a:ibm:guardium_data_protection:*:*:*:*:*:*:*:* is a wildcard, with the EUVD record (EUVD-2026-95241) and the vendor advisory narrowing the affected release to Guardium Data Protection 12.2. The CVSS vector places the attack at the local layer (AV:L) with low privileges required (PR:L), no user interaction (UI:N), and unchanged scope (S:U), while impact is high across confidentiality, integrity, and availability because root on a data-protection appliance exposes the database activity monitoring configuration, audit repositories, and any credentials the appliance manages.
Know when Guardium Data Protection gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Requires local appliance access with low privileges so AV:L/PR:L; hard-coded key makes exploitation low-complexity (AC:L); recovering root yields total compromise, hence C:H/I:H/A:H.
Primary rating from Vendor (ibm).
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
IBM Guardium Data Protection 12.2 is vulnerable due to weak cryptographic protection and a hard-coded recovery key in the pkcrypto passkey component. A local attacker could exploit this vulnerability to recover the root password and gain root privileges.
Executive ViewAI
IBM Guardium Data Protection 12.2 contains a local privilege escalation flaw that lets an attacker who already holds a low-privilege foothold on the appliance recover the root password and take full control of the system. Because Guardium appliances are typically the custodians of database activity monitoring and audit data, root compromise by a malicious insider or a previously breached host could expose or undermine the integrity of sensitive monitoring and compliance records. Leadership should treat this as a contained but serious insider-risk and host-hardening issue rather than an externally exploitable threat.
Patch available per vendor advisory. Until patching is complete, limit and monitor local access to the appliance, enforce least privilege for local accounts, log and alert on access to the pkcrypto/passkey component, and rotate root and administrative credentials accessible from low-privilege local sessions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Guardium Data Protection
View allSQL injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker to execute arbitrary SQL comma
Unauthenticated remote attackers can bypass security restrictions in IBM Guardium Data Protection 12.2 through the Chang
Missing authentication in the LoadBalancerServlet of IBM Guardium Data Protection 12.2 allows unauthenticated, network-r
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the app
Unauthenticated path traversal in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can be leveraged by remote attackers
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2
Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based ac
Missing authentication on a critical management function in IBM Guardium Data Protection 12.2 and 12.2.2 allows unauthen
Missing authentication in the edge-controller component of IBM Guardium Data Protection 12.1 and 12.2.2 allows unauthent
Unauthenticated SQL injection in IBM Guardium Data Protection 12.2 lets a remote attacker submit crafted input that is c
A heap-based buffer overflow in IBM Guardium Data Protection's S-TAP TrafficTap TDS login reassembly routine allows an u
Second-order SQL injection in IBM Guardium Data Protection 12.2 allows an unauthenticated remote attacker to submit SQL
EUVD-2026-95241
GHSA-w6m4-423c-jp5h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB