Cyber & AI intelligence
Wasteland.
Briefs indexed3530
Issues35
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-17049 2026-11-07

IBM API Connect CVE-2026-17049: Critical Authorization Bypass Exposes and Alters Documents

"A critical (CVSS 9.9) authorization bypass in IBM API Connect 12.1.0.0 through 12.1.1.2 could let a remote, authenticated attacker read sensitive information and modify arbitrary documents."

A critical (CVSS 9.9) authorization bypass in IBM API Connect 12.1.0.0 through 12.1.1.2 could let a remote, authenticated attacker read sensitive information and modify arbitrary documents.

What Is It

CVE-2026-17049 is an authorization bypass through user-controlled keys (CWE-639) in IBM API Connect. IBM's description says a remote authenticated attacker could exploit the flaw to "obtain sensitive information and modify arbitrary documents." Flaws in this class usually happen when an application trusts an identifier supplied by the user and doesn't check that the requester is allowed to access the object it points to.

IBM PSIRT published the record to NVD on 2026-11-07. NVD lists it as "Awaiting Analysis," so NVD has not yet added its own enrichment.

Why It Matters

IBM gives the flaw a CVSS v3.1 base score of 9.9 (Critical), with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. In plain terms:

API Connect is an API management platform, so it often sits in front of many back-end services. If a low-privileged user can read and modify documents across authorization boundaries, that is a serious risk on any multi-tenant or widely provisioned deployment.

Exploitation status: The supplied CISA KEV data has no entry for this CVE. Active exploitation is not confirmed by KEV at this time, and no CISA-mandated remediation deadline applies.

What's Vulnerable

The supplied data lists no other products or version branches.

Patch Status

The NVD record does not give a fixed version or specific remediation steps. IBM's security bulletin (linked below) is the authoritative source for fixes, interim fixes and mitigations. Organizations running API Connect 12.1.0.0–12.1.1.2 should:

Because the CVE is not in KEV, CISA has issued no required action or federal due date.

Sources