Quick answers
- Is CVE-2026-17405 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17405 being exploited in the wild.
- How severe is CVE-2026-17405?
- High severity, with a CVSS score of 8.8, published 7 November 2026.
- Which products and versions are affected?
- IBM API Connect 10.0.8.0–10.0.8.12, 12.1.0.0–12.1.1.2.
- Is there a fix for CVE-2026-17405?
- Yes: fixed in API Connect 10.0.8.13, 12.1.1.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17405 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-17405?
- Check whether you run IBM API Connect 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.
How to fix
- Fixed in: API Connect 10.0.8.13, 12.1.1.3
Technical details
The vulnerability is a broken object-level authorization flaw (CWE-639) in the keystore access controls. An authenticated attacker can bypass authorization checks on keystore objects and retrieve sensitive key material. The attack requires prior authentication but no other preconditions; the fix exists in versions 10.0.8.13+ and 12.1.1.3+.
Affected products
- IBM API Connect 10.0.8.0–10.0.8.12, 12.1.0.0–12.1.1.2
Timeline
- 2026-11-07: disclosed