IBM Guardium Data Protection 12.2.2, and 12.1 could allow a remote attacker to delete arbitrary files due to improper limitation of a pathname to a restricted directory.
CVE-2026-82900
HIGHPre-NVD 8.18.1—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-09. A secondary CVSS source baseline 8.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 8.1
- EG Score
- 8.1HIGHhigh confidence
- EG Risk
- 41EG Risk 41/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.4%
- EPSS %ILE
- 27th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 8, 2026
Last Modified
October 9, 2026
Advisory Details (1)
Auto-updated Oct 8, 2026No fix on record yet.
genericMentions a patch (unverified)
Security Bulletin: IBM Guardium Data Protection is affected by multiple vulnerabilities.
https://www.ibm.com/support/pages/node/7288832Vendor Advisories for CVE-2026-82900(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 20:07 UTCEPSS rescore
- 2026-10-09 17:05 UTCGHSA enrichment
- 2026-10-09 11:17 UTCEG score recompute
- 2026-10-09 11:17 UTCGHSA enrichment
- 2026-10-08 22:22 UTCEG score recompute
- 2026-10-08 21:43 UTCEG score recompute
- 2026-10-08 21:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-82900?
CVE-2026-82900 is a high vulnerability published on October 8, 2026. IBM Guardium Data Protection 12.2.2, and 12.1 could allow a remote attacker to delete arbitrary files due to improper limitation of a pathname to a restricted directory.
When was CVE-2026-82900 disclosed?
CVE-2026-82900 was first published on October 8, 2026, with the most recent update on October 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82900 actively exploited?
CVE-2026-82900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82900?
CVE-2026-82900 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82900?
No fix for CVE-2026-82900 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-82900 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82900
Is Your Infrastructure Affected by CVE-2026-82900?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.