IBM API CONNECT · CVE-2026-17297 · Vendor
FIX → 10.0.8.13 · 12.1.1.3 ✓ verified
IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 do not validate the redirect address used during sign-in. An attacker can send authentication results to a location they control, which leads to account takeover.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running self-managed IBM API Connect 10.0.8.0 through 10.0.8.12 or 12.1.0.0 through 12.1.1.2 (v12 OnPrem). The attacker needs no account, but the CVSS vector requires user interaction, so a user likely has to follow a crafted sign-in link; IBM does not describe the exact flow. Teams on 10.0.8.13 or 12.1.1.3 or later can skip it.
Not affected if unaffected-version
Who cares ibm-api-connect, self-hosted
10.0.8.0 through 10.0.8.12 (fixed in 10.0.8.13) and 12.1.0.0 through 12.1.1.2 (fixed in )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 attacker to perform an account takeover due to an open redirect vulnerability. The redirect address used during sign-in is not sufficiently validated, which could allow authentication results to be sent to an attacker-controlled location.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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.
12.1.1.310.0.8.13 bulletin's metadata says V10.0.8.0 - V10.0.8.13, but its table and fix say 10.0.8.12 is the last affectedUpgrade to 10.0.8.13 · 12.1.1.3
10.0.8.x to 10.0.8.13, or 12.1.x to 12.1.1.3 (IBM Fix Central)