API CONNECT V12 ONPREM · CVE-2026-19121 · Vendor
FIX → 12.1.1.3 ✓ verified
IBM API Connect versions 12.1.0.0 through 12.1.1.2 do not check that a signed-in user belongs to the tenant they are acting in. A logged-in attacker can gain unauthorized access to another tenant's resources.
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 self-managed (OnPrem) IBM API Connect V12, versions 12.1.0.0 through 12.1.1.2, with more than one tenant are exposed: a logged-in user can reach another tenant's resources because tenant context is not checked against the user. IBM lists no workaround, so upgrade to 12.1.1.3. IBM does not list other versions as affected.
Not affected if outside-affected-range, single-tenant
Who cares api-gateway, ibm-api-connect, multi-tenant, self-hosted
v12.1.0.0 through v12.1.1.2; fixed in v12.1.1.3IBM API Connect 12.1.0.0 through 12.1.1.2 could allow an authenticated attacker to gain unauthorized access due to improper authorization. Tenant context is not sufficiently verified against the authenticated user, which could allow access to another tenant's resources.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
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.
Upgrade to 12.1.1.3
Upgrade IBM API Connect to v12.1.1.3 (Fix Central: https://www.ibm.com/support/pages/node/7290205)