CVE-2026-108178 · Infrastructure
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 have an incomplete token validation check. Under certain conditions, a token may be accepted for a purpose it was not intended for.
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 running IBM API Connect in the affected version ranges, 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2. The sources do not say which deployment conditions make token validation incomplete, so exposure beyond the version range is unknown.
Not affected if unknown
Who cares api-gateway, ibm-api-connect
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 token to be accepted that should be rejected due to an improperly implemented security check. Under certain conditions, token validation is incomplete, so a token may be accepted for a purpose it was not intended for.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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.