CVE-2026-82896: IBM Guardium Data Protection · Path Traversal
Affects IBM Guardium Data ProtectionSource CVE Database V5
Not known to be exploited · CVSS 7.6 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-19.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 18 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMGuardium Data Protection | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:ibm:guardium_data_protection:12.2:*:*:*:*:*:*:*cpe:2.3:a:ibm:guardium_data_protection:12.2.0:*:*:*:*:*:*:*
AI-suggested
Since the vulnerability requires authentication, restricting access to trusted users and monitoring for suspicious activity is advisable. Check IBM's official advisories for updates on patches or fixes.
Description
IBM Guardium Data Protection version 12.2 contains a path traversal vulnerability (CWE-22) that could allow a remote authenticated attacker to traverse directories on the system. This vulnerability has a CVSS 3.1 score of 7.6, indicating high severity with low attack complexity but requiring authentication. The flaw could lead to limited confidentiality impact, high integrity impact, and low availability impact.