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.
Advisories
No advisories yet.
Fixes
Solution
IBM strongly recommends addressing the vulnerability now by upgrading to v12.1.1.3 Fix Central Link: https://www.ibm.com/support/pages/node/7290205
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://www.ibm.com/support/pages/node/7295635 |
|
History
Sat, 07 Nov 2026 04:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Multiple Vulnerabilities in IBM API Connect | |
| First Time appeared |
Ibm
Ibm api Connect |
|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:ibm:api_connect:12.1.0.0:*:*:*:*:*:*:* cpe:2.3:a:ibm:api_connect:12.1.1.2:*:*:*:*:*:*:* |
|
| Vendors & Products |
Ibm
Ibm api Connect |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: ibm
Published:
Updated: 2026-11-07T04:33:04.239Z
Reserved: 2026-07-25T01:28:32.431Z
Link: CVE-2026-17312
No data.
No data.
No data.
OpenCVE Enrichment
No data.
Weaknesses