CVE-2026-11930

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.9 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-08) is not newer than that change (2026-10-09), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 may not enforce authorization correctly for some web servers.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 8, 2026

Last Modified

October 9, 2026

Advisory Details (1)

Auto-updated Oct 9, 2026
Fix referenced — no release confirmed yet.
Web page

Security Bulletin: Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access

https://www.ibm.com/support/pages/node/7291628

Vendor Advisories for CVE-2026-11930(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 24× in last 7d / 24× 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.

  1. 2026-10-11 23:41 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  2. 2026-10-11 20:12 UTCEG score recompute
  3. 2026-10-11 18:25 UTCEG score recompute
  4. 2026-10-11 14:58 UTCEG score recompute
  5. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-11 12:31 UTCEG score recompute
  7. 2026-10-11 12:31 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  8. 2026-10-11 01:09 UTCEG score recompute
  9. 2026-10-11 01:09 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-10 13:56 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  12. 2026-10-10 02:44 UTCEG score recompute
  13. 2026-10-10 02:44 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-09 15:34 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  16. 2026-10-09 15:01 UTCEG score recompute
  17. 2026-10-09 15:01 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  18. 2026-10-09 14:46 UTCEG score recompute▲ 1.60
  19. 2026-10-09 14:45 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  20. 2026-10-09 14:31 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  21. 2026-10-08 21:37 UTCEG score recompute
  22. 2026-10-08 21:37 UTCGHSA enrichmentGHSA-fpg9-wj5q-fhvg · GitHub CVSS 5.9
  23. 2026-10-08 21:19 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  24. 2026-10-08 21:18 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-11930?
CVE-2026-11930 is a high-severity vulnerability; its CVE record was published on October 8, 2026. IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 may not enforce authorization correctly for some web servers.
When was the CVE record for CVE-2026-11930 published?
The CVE record for CVE-2026-11930 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-11930 actively exploited?
CVE-2026-11930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11930?
CVE-2026-11930 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-11930?
A fix for CVE-2026-11930 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-11930 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11930

Explore →

Is Your Infrastructure Affected by CVE-2026-11930?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs