CVE-2026-105459 · Vendor
NO FIX YET
IBM API Connect accepts a token without fully verifying its cryptographic signature in affected 10.0.8.x and 12.1.x releases. An attacker can use this to join an organization without a valid invitation.
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 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 are exposed. The sources do not say which deployment configurations are affected beyond the version ranges.
Not affected if unknown
Who cares api-connect, ibm, 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 an attacker to gain unauthorized access to an organization due to improper verification of a cryptographic signature. A token is accepted without its signature being fully verified, which could allow an attacker to join an organization without a valid invitation.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/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.