IBM API CONNECT · CVE-2026-17291 · 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 OAuth 2.0 sign-in. An authenticated remote attacker can send sign-in results to an attacker-controlled location, 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.
Self-managed IBM API Connect installs on 10.0.8.0-10.0.8.12 or 12.1.0.0-12.1.1.2. The OAuth 2.0 sign-in redirect address is not validated, so a logged-in low-privilege attacker who gets a user to follow a crafted link can send that user's sign-in result to an attacker-controlled site and take over the account. Teams not running API Connect, or already on 10.0.8.13 / 12.1.1.3, can skip it.
Not affected if unaffected-version
Who cares ibm-api-connect, oauth, open-redirect, self-hosted
10.0.8.0 to 10.0.8.12, and 12.1.0.0 to (IBM lists V12 OnPrem)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 perform account takeover due to an open redirect vulnerability. The redirect address used during OAuth 2.0 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:L/UI:R/S:C/C:H/I:H/A:N
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.210.0.8.13 and 12.1.1.3Upgrade to 10.0.8.13 · 12.1.1.3
10.0.8.13 (10.0.8 line) or 12.1.1.3 (12.1 line)NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.