CVE-2026-17202 · Runtime
NO FIX YET
IBM API Connect 12.1.0.0 through 12.1.1.2 returns observably different responses depending on whether a username exists. A remote attacker can use this to build a list of valid usernames for later password guessing or phishing.
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 12.1.0.0 through 12.1.1.2 with a reachable login or user-facing endpoint are exposed. The sources do not say which endpoints leak the difference or whether a default configuration is affected. Deployments outside that version range can skip it.
Not affected if outside-affected-versions
Who cares api-gateway, ibm-api-connect, self-hosted
No fix yet, per the sources.
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to enumerate usernames due to observable differences in response behavior.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.