IBM API CONNECT V12 ONPREM · CVE-2026-17337 · Runtime
FIX → 12.1.1.3 ✓ verified
IBM API Connect V12 OnPrem v12.1.0.0 through v12.1.1.2 does not perform a certificate check reliably in all cases, so a connection may be accepted without proper authentication. IBM fixed it in v12.1.1.3 and lists no workarounds.
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 (on-prem) IBM API Connect V12 deployments running v12.1.0.0 through v12.1.1.2. A certificate check is not performed reliably in all cases, so a connection may be accepted without proper authentication. IBM's bulletin lists only API Connect V12 OnPrem; other editions and versions are not listed as affected. IBM does not state a required configuration.
Not affected if versions-outside-12.1.0.0-to-12.1.1.2
Who cares api-gateway, ibm-api-connect, self-hosted
v12.1.0.0 and v12.1.1.2 inclusive; v12.1.1.3 or later is fixedIBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to bypass authentication due to improper certificate validation. A certificate check is not performed reliably in all cases, which could allow a connection to be accepted without proper authentication.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
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
Upgrade IBM API Connect to v12.1.1.3 (Fix Central: https://www.ibm.com/support/pages/node/7290205)