CVE-2026-17312 · Infrastructure
NO FIX YET
IBM API Connect versions 12.1.0.0 through 12.1.1.2 do not sufficiently verify that a login response belongs to the user's own sign-in request. A remote attacker can use cross-site request forgery to make a victim sign into an attacker-controlled account and link the victim's session to it.
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 that run IBM API Connect in the 12.1.0.0 to 12.1.1.2 range are affected through its sign-in flow. The sources do not say which deployment settings change exposure, so the sources do not establish who can skip it.
Who cares 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 force a user to authenticate into an attacker-controlled account due to cross-site request forgery. The sign-in flow does not sufficiently verify that a login response belongs to the user's own request, which could link the victim's session to an account controlled by the attacker.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.