CVE-2026-17066 · Vendor
NO FIX YET · SEE WHAT TO DO
IBM API Connect versions 12.1.0.0 through 12.1.1.2 lack an authorization check, so a logged-in user can read, modify or delete data belonging to other tenants. The attacker needs a valid account on the platform, and the impact is cross-tenant data exposure and tampering.
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 12.1.0.0 through 12.1.1.2, especially multi-tenant deployments where several teams or customers share one instance. Single-tenant installs on other versions are not in the stated range. The attacker must already hold an authenticated account on the platform.
Not affected if no-authenticated-users, single-tenant, version-outside-range
Who cares api-connect, ibm, multi-tenant, self-hosted
12.1.0.0 through 12.1.1.2.12.1.1.2 as stated in IBM's advisory; the exact fixed version is unknown from the sources.IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information and modify or delete data belonging to other tenants due to missing authorization.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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.