How severe is CVE-2026-11930?

CVE-2026-11930 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which products are affected by CVE-2026-11930?

CVE-2026-11930 affects the following products: ibm security verify access, ibm security verify access container, ibm verify identity access, ibm verify identity access container.

How do I patch CVE-2026-11930?

No patch has shipped for CVE-2026-11930 yet — track the ibm security verify access advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2026-11930 across my infrastructure?

Inventory every ibm security verify access deployment and check each version against the affected-products list above.

How do I mitigate CVE-2026-11930 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2026-11930 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-11930 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-11930?

CVE-2026-11930 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-11930?

CVE-2026-11930 is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2026-11930?

CVE-2026-11930 affects ibm security verify access (3 versions, e.g. 10.0, 10.0.0, 10.0.9.2); ibm security verify access container (3 versions, e.g. 10.0, 10.0.0, 10.0.9.2); ibm verify identity access (3 versions, e.g. 11.0, 11.0.0, 11.0.3); ibm verify identity access container (3 versions, e.g. 11.0, 11.0.0, 11.0.3). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-11930 published, and has it been updated?

CVE-2026-11930 was published on October 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

MEDIUM severity

CVE-2026-11930 — Security Verify Access

MEDIUM

CVE-2026-11930 is a medium-severity (CVSS 5.9) CWE-285 vulnerability in ibm security verify access. No vendor fix is recorded yet; mitigation options are listed below.

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.

Published

Oct 8, 2026

Updated

Oct 8, 2026

Affected

4 products

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-11930 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

4 products · 12 configurations

Application

security verify accessibm

3 versions

10.010.0.010.0.9.2

Application

security verify access containeribm

3 versions

10.010.0.010.0.9.2

Application

verify identity accessibm

3 versions

11.011.0.011.0.3

Application

verify identity access containeribm

3 versions

11.011.0.011.0.3

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every ibm security verify access deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2026-11930 yet — track the ibm security verify access advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

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.

O3 Security · Runtime Protection

Is CVE-2026-11930 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works

CVE-2026-11930 — Security Verify Access

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2026-11930 being exploited in your environment?