CVE-2026-17406 · Infrastructure
NO FIX YET · SEE WHAT TO DO
IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 fail to block some internal destinations when the server makes requests. A remote attacker with an account can use this to reach blocked addresses and obtain sensitive information.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running IBM API Connect in the affected version ranges are exposed, and the attacker needs a valid account on the platform. Deployments outside those ranges are not affected. The sources do not describe further configuration conditions.
Not affected if outside-affected-versions
Who cares api-gateway, ibm-api-connect, self-hosted
10.0.8.0 to 10.0.8.12 and 12.1.0.0 to 12.1.1.210.0.8.12 or 12.1.1.2, per the vendor's fixed versions: exact fixed version unknown from the sourcesIBM 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 server-side request forgery. Address checks can be bypassed, which could allow the server to reach destinations that should be blocked.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/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.