API CONNECT · CVE-2026-17112 · Infrastructure
FIX → 10.0.8.13 · 12.1.1.3 ✓ verified
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 user can read sensitive information that belongs to other tenants.
first public Nov 7, 2026 · 2 sources
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 10.0.8.0-10.0.8.12 or V12 OnPrem 12.1.0.0-12.1.1.2. Any logged-in user can read sensitive information that belongs to other tenants because object-level permissions are not checked, so shared multi-tenant instances are the main concern. IBM's bulletins do not name the API endpoints. Single-tenant installs have less exposure, and anyone already on 10.0.8.13 or 12.1.1.3 can skip it.
Not affected if outside-affected-versions, single-tenant
Who cares api-management, ibm-api-connect, multi-tenant
10.0.8.0 to 10.0.8.12, and V12 OnPrem 12.1.0.0 to 12.1.1.2IBM 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 belonging to other tenants 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:H/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.
10.0.8.13 and 12.1.1.3Upgrade to 10.0.8.13 · 12.1.1.3
10.0.8.13 (10.0.8 line) or v12.1.1.3 (v12 line)