Quick answers
- Is CVE-2026-17616 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17616 being exploited in the wild.
- How severe is CVE-2026-17616?
- Medium severity, with a CVSS score of 6.8, published 12 August 2026.
- Which products and versions are affected?
- IBM Security Verify Access 10.0 through 10.0.9.2; IBM Verify Identity Access 11.0 through 11.0.3; IBM Verify Identity Access Container 11.0 through 11.0.3.
- Is there a fix for CVE-2026-17616?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-17616 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-17616?
- Check whether you run IBM Security Verify Access, IBM Verify Identity Access or IBM Verify Identity Access Container at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a cryptographic validation weakness (CWE-310) in the reverse proxy component of IBM's identity and access management platform. The vulnerability affects the cryptographic validation of user-supplied data in specific configurations, allowing attackers to bypass or weaken the integrity checks on authentication-related data. An attacker with low privileges (PR:L) can exploit this over the network (AV:N) through non-standard conditions (AC:H) to gain unauthorized access to confidential information and modify data (C:H, I:H). The vulnerability requires authentication credentials to exploit. Patches have been released by IBM for affected versions.
Affected products
- IBM Security Verify Access 10.0 through 10.0.9.2
- IBM Verify Identity Access 11.0 through 11.0.3
- IBM Verify Identity Access Container 11.0 through 11.0.3
Timeline
- 2026-08-12: disclosed