---
title: "CVE-2026-19121: IBM API Connect - Broken Access Control"
description: "IBM API Connect 12.1.0.0 through 12.1.1.2 contains a broken access control caused by insufficient tenant context verification against authenticated users, letting authenticated attackers access other tenants' resources."
url: https://panop.io/threat-heartbeat/CVE-2026-19121/
---

# CVE-2026-19121 IBM API Connect - Broken Access Control

IBM API Connect 12.1.0.0 through 12.1.1.2 contains a broken access control caused by insufficient tenant context verification against authenticated users, letting authenticated attackers access other tenants' resources.

CVSS base score 8.3 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.37% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-19121)

## Details

Type

Broken Access Control

Impact

Broken Access Control, Information Disclosure, Data Tampering

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Published

7 November 2026

Updated

9 November 2026

Weakness

[CWE-290](https://cwe.mitre.org/data/definitions/290.html)

## Vendor fix

Upgrade to a version later than 12.1.1.2 or the latest available version.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-19121](https://nvd.nist.gov/vuln/detail/CVE-2026-19121)
- [https://www.ibm.com/support/pages/node/7295635](https://www.ibm.com/support/pages/node/7295635)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
