IBM API CONNECT · CVE-2026-17405 · Infrastructure
FIX → 12.1.1.3 · 10.0.8.13 ✓ verified
IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 do not check whether a logged-in user may read keystore objects. A remote authenticated attacker can therefore read keystore information they should not see.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Self-managed IBM API Connect deployments on 10.0.8.0 to 10.0.8.12 or 12.1.0.0 to 12.1.1.2. An attacker needs a valid login; the keystore access check does not confirm the user may read the keystore object, so keystore information can be exposed. Teams not running API Connect can skip it.
Not affected if auth-required, version-outside-range
Who cares api-gateway, auth-required, ibm-api-connect, self-hosted
10.0.8.0-10.0.8.12 or 12.1.0.0-12.1.1.2 is affected10.0.8.13, 12.1.1.3IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to broken object-level authorization. Access checks on keystore objects do not confirm that the requesting user is permitted to read them, which could expose keystore information.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 12.1.1.3 · 10.0.8.13
10.0.8.13 (IBM bulletin) or 12.1.1.3 (per CVE record vendor solution; 12.1.1.3 bulletin text read was truncated)