CVE-2026-17287 · 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 validate user-supplied addresses, enabling server-side request forgery. A logged-in attacker can make the server send requests to unintended destinations and receive the results, exposing 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 10.0.8.x up to 10.0.8.12 or 12.1.x up to 12.1.1.2. An attacker needs a valid account on the platform, so deployments that restrict or do not expose authenticated access are at lower risk. unknown for which specific features are required to trigger it.
Not affected if fixed-version, unauthenticated-only-access
Who cares api-gateway, ibm-api-connect, self-hosted
10.0.8.12 and 12.1.1.2IBM 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. User-supplied addresses are not sufficiently validated, so the server could be made to send requests to unintended destinations and return the results.
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.