CVE-2026-17371 · 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 check object-level permissions. A logged-in attacker can read sensitive information belonging to other users or objects.
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 that run IBM API Connect in the affected version ranges, where authenticated users can reach API objects they should not see. Exposure depends on who holds accounts on the platform; installations without untrusted authenticated users are less exposed. The sources do not describe the specific endpoints or default configuration.
Not affected if no-untrusted-accounts, unaffected-version
Who cares ibm-api-connect, self-hosted
unknown for the exact check command, the sources do not say.10.0.8.0 through 10.0.8.12 or 12.1.0.0 through 12.1.1.2.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 sensitive information due to broken object-level authorization.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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.