IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 and IBM Verify Identity Access Container 11.0 through 11.0.3 contains a input validation vulnerability in the management interface that allows already privileged attackers to execute additional operations by crafting a malicious HTTP request.
CVE-2026-12005
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. a secondary CVSS source baseline 7.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
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 computedSeverity72% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
August 17, 2026
Advisory Details (1)
Auto-updated Aug 12, 2026Security Bulletin: Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
https://www.ibm.com/support/pages/node/7283079Vendor Advisories for CVE-2026-12005(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 26× in last 7d / 40× 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-08-20 22:55 UTCEG score recompute
- 2026-08-20 22:55 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 10:09 UTCGHSA enrichment
- 2026-08-19 21:24 UTCEG score recompute
- 2026-08-19 21:23 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 08:16 UTCGHSA enrichment
- 2026-08-18 19:31 UTCEG score recompute
- 2026-08-18 19:31 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 06:45 UTCGHSA enrichment
- 2026-08-17 17:55 UTCEG score recompute
- 2026-08-17 17:55 UTCGHSA enrichment
- 2026-08-17 07:43 UTCGHSA enrichment
- 2026-08-16 18:58 UTCEG score recompute
- 2026-08-16 18:58 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:12 UTCEG score recompute
- 2026-08-16 06:12 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:27 UTCGHSA enrichment
- 2026-08-15 04:41 UTCEG score recompute
- 2026-08-15 04:41 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
Show 15 moreShow fewer
- 2026-08-14 15:55 UTCGHSA enrichment
- 2026-08-14 03:10 UTCEG score recompute
- 2026-08-14 03:10 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 14:24 UTCEG score recompute
- 2026-08-13 14:24 UTCGHSA enrichment
- 2026-08-13 13:56 UTCEG score recompute
- 2026-08-13 13:56 UTCGHSA enrichment
- 2026-08-13 05:19 UTCEG score recompute
- 2026-08-13 05:19 UTCGHSA enrichment
- 2026-08-13 04:21 UTCEG score recompute
- 2026-08-13 04:21 UTCGHSA enrichment
- 2026-08-12 20:19 UTCEG score recompute
- 2026-08-12 20:06 UTCEG score recompute
- 2026-08-12 20:05 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-12005?
When was CVE-2026-12005 disclosed?
Is CVE-2026-12005 actively exploited?
What is the CVSS score of CVE-2026-12005?
How do I remediate CVE-2026-12005?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12005
Is Your Infrastructure Affected by CVE-2026-12005?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.