CVE-2026-19121: IBM API Connect improper authorization in tenant context

CVE-2026-19121 · Severity: high · CVSS 8.3 · Published 2026-11-07

IBM API Connect is a platform for managing and securing APIs used by enterprises. In affected versions, an authenticated user can access resources belonging to another tenant due to insufficient verification of tenant context, allowing unauthorized data exposure across multi-tenant deployments.

Technologies: IBM API Connect. Vendors: IBM.

Quick answers

Is CVE-2026-19121 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-19121 being exploited in the wild.
How severe is CVE-2026-19121?
High severity, with a CVSS score of 8.3, published 7 November 2026.
Which products and versions are affected?
IBM API Connect 12.1.0.0 through 12.1.1.2.
Is there a fix for CVE-2026-19121?
Yes: fixed in 12.1.1.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-19121 attacked?
It is attacked over the network.
Am I affected by CVE-2026-19121?
Check whether you run IBM API Connect at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 12.1.1.3

Technical details

The vulnerability is an improper authorization flaw where tenant context is not sufficiently verified against the authenticated user, allowing access to another tenant's resources. It requires prior authentication but no additional user interaction. An attacker gains unauthorized access to cross-tenant data within the same API Connect deployment.

Affected products

  • IBM API Connect 12.1.0.0 through 12.1.1.2

Timeline

  • 2026-11-07: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.