IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow an attacker with administrative privileges and access to the local management interface to execute arbitrary code due to an unbounded write to a fixed-size stack buffer.
CVE-2026-12109
This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.2
- EG Score
- 7.2HIGHmedium confidence
- EG Risk
- 32EG Risk 32/100
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 computed (value × EchelonGraph’s weight)Severity72% × 45%The EG Score, 7.2 of 10.Exploitation0% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 10th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
Published
October 8, 2026
Last Modified
October 10, 2026
Advisory Details (1)
Auto-updated Oct 9, 2026Security Bulletin: Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
https://www.ibm.com/support/pages/node/7291628Vendor Advisories for CVE-2026-12109(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 22× in last 7d / 22× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-11 01:57 UTCEG score recompute
- 2026-10-11 01:57 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-10 13:24 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-10 12:35 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-10 04:22 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-10 04:10 UTCEG score recompute
- 2026-10-10 04:10 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-10 03:29 UTCEG score recompute
- 2026-10-10 03:29 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-10-09 14:57 UTCEG score recompute▲ 1.70
- 2026-10-09 14:56 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-09 14:31 UTCNVD updateCVSS v3 → 7.2 · severity → HIGH
- 2026-10-09 12:33 UTCEG score recompute
- 2026-10-09 12:32 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-09 12:06 UTCEG score recompute
- 2026-10-09 12:06 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-08 21:37 UTCEG score recompute
- 2026-10-08 21:37 UTCGHSA enrichmentGHSA-fcc9-gh9q-v8qc · GitHub CVSS 5.5
- 2026-10-08 21:19 UTCEG score recompute
- 2026-10-08 21:18 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-12109?
When was the CVE record for CVE-2026-12109 published?
Is CVE-2026-12109 actively exploited?
What is the CVSS score of CVE-2026-12109?
How do I remediate CVE-2026-12109?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12109
Is Your Infrastructure Affected by CVE-2026-12109?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.