Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain hard-coded key from software
-
ExploitAccess network-exposed encrypted data
-
ImpactDecrypt protected sensitive information
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Exploitation Conditions | Exploitation requires IBM Guardium Data Protection version 12.1 or 12.2, where a static cryptographic key is compiled into the product and therefore identical across every installation; an attacker must recover that key from the shipped software and then be able to access the ciphertext it protects. The CVSS High attack complexity (AC:H) is the main limiting factor - the attacker must obtain the key and be positioned to intercept or read the protected data rather than exploiting via a single unauthenticated request. No user interaction or authentication is required per the vector (UI:N/PR:N), but realistic exploitation is gated by access to the encrypted sensitive data in a given deployment. |
| Impact | This is a genuinely notable issue but not a top-tier emergency. The CVSS base score of 8.1 (AV:N/AC:H/PR:N/UI:N) reflects an unauthenticated, network-reachable weakness, but the High attack complexity (AC:H) is significant: exploiting a hard-coded cryptographic key (CWE-321) typically requires the attacker to first obtain the key from the shipped software and then be positioned to intercept or access the protected ciphertext, rather than firing a single request. No EPSS score, CISA KEV listing, SSVC decision data, or public POC was provided in the input, so there is no evidence of active or probable near-term exploitation; by the precision rules this is 'no public exploit identified at time of analysis.' A key conflict to flag: the IBM description characterizes the impact strictly as an attacker obtaining sensitive information (a confidentiality issue), yet the supplied CVSS vector asserts C:H/I:H/A:H (full integrity and availability impact). That is inconsistent - a hard-coded key enabling disclosure does not obviously grant integrity or availability impact - and should be verified against the IBM advisory (node/7293014). Treat this as an important patch-management item for Guardium operators rather than a drop-everything crisis, given AC:H and no exploitation signals. |
| Exploit ScenarioDerived | An attacker extracts the hard-coded cryptographic key embedded in IBM Guardium Data Protection 12.1/12.2 (identical across all installations) and uses it to decrypt sensitive information that the product protects with that key, for example by intercepting network-exposed encrypted data. Because the key is static and network access suffices (AV:N/PR:N), any party who recovers the key from the software can perform this against affected deployments, though the High attack complexity means positioning to access the ciphertext is non-trivial. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Hard-coded cryptographic key in IBM Guardium Data Protection 12.1 and 12.2 means the same static key ships inside every installation, so an attacker who reverse-engineers the product and recovers that key can decrypt (and potentially forge) the data it protects across any deployment. The assessed vector (AV:N/AC:H/PR:N/UI:N) rates this High complexity rather than trivially exploitable, because the attacker must both extract the key and gain access to the ciphertext it guards, and the independent assessment scopes the realistic impact to confidentiality loss rather than integrity or availability. No public exploit code and no CISA KEV listing were identified at time of analysis, and no EPSS score was supplied; the issue is serious but not a top-tier emergency.
RemediationAI
A specific patched build number is not stated in the supplied data, so the primary action is to consult IBM's advisory at https://www.ibm.com/support/pages/node/7293014 (mirrored at https://nvd.nist.gov/vuln/detail/CVE-2026-82891) and apply the fixed release IBM designates for 12.1 and 12.2; because the key is compiled into the product, no customer-side key rotation fully removes exposure until that vendor fix is installed, and any material previously protected by the static key should be treated as potentially decryptable. Until patched, restrict network reachability to Guardium appliance and web interfaces to trusted management segments only, since the vector is AV:N - the trade-off is that distributed collector/aggregator topologies and remote administration paths may need re-architecting through a jump host or VPN concentrator, and port changes must not break appliance registration. Tighten authorization and audit on the ciphertext itself, since exploitation also requires access to the protected data: limit who can read or export audit repositories, backups and archives, alert on bulk reads or downloads of those artifacts, and store off-appliance copies in a separately keyed container. If key compromise is suspected, terminate TLS at a trusted reverse proxy so external sessions are not protected solely by the embedded key, at the cost of added latency and certificate management overhead.
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 root cause is CWE-321, Use of Hard-coded Cryptographic Key: rather than generating or deriving key material per deployment, IBM Guardium Data Protection 12.1 and 12.2 embeds a static cryptographic key in the shipped software. A key compiled into distributable code has no per-install entropy, so every customer instance shares identical key material - recovering it once, for example by unpacking or reverse-engineering the distributed binaries, yields a universal key rather than one victim's key. That defeats the purpose of encryption for stored audit repositories, configuration or other sensitive material the key protects, and cannot be remediated by customer-side rotation because there is nothing deployment-specific to rotate to until the vendor changes the implementation. The AV:N/AC:H/PR:N/UI:N vector reflects that while the attack path requires no credentials or user action, exploitation is gated by two conditions: successful key recovery and the ability to intercept or read the protected ciphertext in a given environment. Note the vendor-advertised score of 8.1 carries C:H/I:H/A:H, whereas the independent assessment scopes impact to C:H/I:N/A:N, treating the issue as an information-disclosure problem; no CPE strings were supplied, and the EUVD record simply enumerates Guardium Data Protection 12.1 and 12.2.
Know when the next one hits your stack
- 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:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Hard-coded key is network-reachable and unauthenticated (AV:N/PR:N) but requires key recovery and ciphertext access (AC:H); impact per description is confidentiality only, so I:N/A:N.
Primary rating from Vendor (us).
CVSS VectorVendor: us
DescriptionCVE.org
IBM Guardium Data Protection 12.1, and 12.2 could allow a remote attacker to obtain sensitive information due to use of a hard-coded cryptographic key.
Executive ViewAI
IBM Guardium Data Protection 12.1 and 12.2 contain a hard-coded cryptographic key shared across installations, creating a confidentiality risk that could extend to every affected deployment if the key is recovered. Leadership should prioritize visibility and containment of these systems because a single reverse-engineering effort plus access to protected ciphertext could expose sensitive data, even though no public exploit was identified at time of analysis.
No vendor-released patch identified at time of analysis; interim mitigations include network segmentation and strict access control around IBM Guardium Data Protection 12.1 and 12.2 deployments, least-privilege administration with strong authentication, enhanced monitoring and alerting for access to protected ciphertext, minimizing data stored in affected environments, and engaging IBM support for key-rotation or fix guidance.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-106863
GHSA-r63h-wh8w-f865
NVD
CVE.org
EPSS
Exploit-DB