API CONNECT V12 ONPREM · CVE-2026-17355 · Vendor
FIX → 12.1.1.3 ✓ verified
IBM API Connect 12.1.0.0 through 12.1.1.2 has a server-side request forgery flaw: destination checks on outbound requests can be bypassed. A remote attacker with an account can make the server reach internal systems it should block and read sensitive information from them.
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.
Teams running self-hosted (on-prem) IBM API Connect V12, versions v12.1.0.0 through v12.1.1.2. An attacker needs a valid low-privilege account, then can bypass destination checks on outbound requests and reach internal systems. IBM lists no workaround. Others, including versions outside this range, can skip it.
Not affected if unknown
Who cares api-gateway, ibm-api-connect, self-hosted, ssrf
v12.1.0.0 through v12.1.1.2 are affected; v12.1.1.3 is fixedIBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information from internal network resources due to server-side request forgery. Destination checks on outbound requests can be bypassed, which could allow the server to reach internal systems that should be blocked.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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)