CVE-2026-17306 · Infrastructure
NO FIX YET
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a server-side request forgery flaw. A remote attacker can make the server send requests to internal network resources and obtain the sensitive information returned.
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.
Organizations running IBM API Connect 12.1.0.0 through 12.1.1.2 where the gateway or API layer can be made to fetch URLs supplied by outside callers. The sources do not say which configurations or features make the flaw reachable, so treat any internet-facing deployment in the affected range as in scope until IBM's advisory is checked.
Not affected if unknown
Who cares api-gateway, ibm-api-connect, self-hosted
12.1.0.0 through 12.1.1.2No fix yet, per the sources.
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information from internal network resources due to server-side request forgery.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/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.