CVE-2026-17372 · Infrastructure
NO FIX YET
IBM API Connect does not sufficiently restrict user-configured webhook destination URLs, so the server can be made to send requests to internal systems. A remote attacker with a valid account can use this to probe 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.
Teams running IBM API Connect in the affected 10.0.8.x or 12.1.x ranges where users can configure webhooks. The sources do not say whether default configurations are affected. Deployments on other versions are not in the stated ranges.
Not affected if version-outside-range
Who cares ibm-api-connect, self-hosted
No 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 probe internal network resources due to insufficient validation of webhook destination URLs. User-configured webhook addresses are not sufficiently restricted, so the server could be made 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.