CVE-2026-17302 · Infrastructure
NO FIX YET
IBM API Connect 12.1.0.0 through 12.1.1.2 does not properly validate a user-supplied URL. A logged-in remote attacker can use this to probe internal network services from the server.
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.
IBM API Connect deployments in the affected range 12.1.0.0 through 12.1.1.2 are exposed to authenticated users who can submit a URL. The sources do not say which feature takes the URL or what default configuration applies. Teams on other versions can skip it.
Not affected if outside-affected-versions
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 authenticated attacker to probe internal network services due to improper validation of a user-supplied URL.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/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.