CVE-2026-17370 · Vendor
NO FIX YET
IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 fail to verify the identity of the user completing sign-in. A remote attacker who already has an account can obtain an access token belonging to another user and act as that user.
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.
Organizations running IBM API Connect in the affected version ranges, where users can sign in to the platform. The sources do not describe a non-default configuration requirement. unknown whether a specific deployment mode is required.
Not affected if unaffected-versions
Who cares api-gateway, ibm-api-connect, self-hosted
No fix yet, per the sources.
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 obtain an access token for another user due to improper authentication. The sign-in flow does not sufficiently verify the identity of the user completing it, which could allow another user's identity to be assumed.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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.