CVE-2026-8861: Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: security verify access 10.0.9.2; verify identity access 11.0.3 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
IBM Security Verify could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.
- weakness
- CWE-209 Generation of Error Message Containing Sensitive Information
- affected
- IBM Verify Identity Access; IBM Security Verify Access; IBM Verify Identity Access Container; IBM Security Verify Access Container
- published ranges
- ibm security verify access >= 10.0.0 < 10.0.9.2; ibm security verify access container >= 10.0.0.0 <= 10.0.9.1; ibm verify identity access >= 11.0 < 11.0.3; ibm verify identity access container >= 11.0.0.0 <= 11.0.2
- first unaffected version, by branch
- security verify access 10.0.9.2; verify identity access 11.0.3
- severity
- 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- assigned by
- ibm
- published
- 2026-07-17
check us ibm.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 18 Jul 2026 | 0.0024 | |
| 28 Aug 2026 | 0.00402 |
2 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-08-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: security verify access 10.0.9.2; verify identity access 11.0.3. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-8861', '2026-10-30T23:59:59.999999Z', now());