CVE-2026-17303 · Vendor
NO FIX YET
IBM API Connect does not sufficiently restrict a user-supplied URL, so the server can be made to contact internal systems. A remote attacker with a valid account can use the server to reach internal network resources.
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.
Organisations running IBM API Connect in the affected version ranges, where authenticated users can supply a URL the server then fetches. The sources do not say which features accept a URL, so whether a given deployment is exposed is unknown. Teams on versions outside the listed ranges are not affected.
Not affected if version-outside-range
Who cares ibm-api-connect, self-hosted
10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2No fix yet, per the sources.
IBM 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 access internal network resources due to improper validation of a user-supplied URL. The address is not sufficiently restricted, which could allow the server to contact internal systems.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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.