Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
DeliverySend crafted request to API Connect
-
ExploitTrigger confused-deputy component
-
ExecutionPrivileged action executed on attacker's behalf
-
ImpactBypass security restrictions and impact data/service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service Proxy/intermediary controls
|
| Exploitation Conditions | Exploitation requires the attacker to already possess valid authenticated credentials on an IBM API Connect instance in the 12.1.0.0 through 12.1.1.2 range (PR:L), reachable over the network (AV:N), with no user interaction (UI:N) and low attack complexity (AC:L). The limiting factor is this authentication requirement - the attacker must first obtain a low-privilege account - but no special non-default configuration, platform, or feature toggle is named in the description as a prerequisite; the precise feature or protocol path that enables the confused-deputy behavior is not described in the available sources. Deployments restricted to trusted internal users or with no untrusted account provisioning reduce realistic exposure. |
| Impact | This is a genuine high-priority issue, though the public data is thin. The vendor-supplied CVSS of 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) describes a network-reachable, low-complexity flaw requiring only low-privilege authentication (PR:L), with a scope change (S:C) and high confidentiality, integrity, and availability impact - consistent with a confused-deputy (CWE-441) weakness where an already-authenticated, limited-privilege user coaxes a more-privileged component into acting on their behalf, crossing a trust boundary. The vuln.today decision label is act_now and IBM has published a patch, which raises urgency. However, the signals are not fully corroborated: no EPSS probability is supplied, there is no CISA KEV listing, and no public PoC or exploit reference is provided, so there is no public exploit identified at time of analysis. The absence of EPSS/KEV means exploitation likelihood cannot be quantified from the input and should not be inferred; the high score reflects potential impact and ease given valid credentials, not evidence of mass exploitation. The description is terse and does not state the exact mechanism, affected feature, or which security restriction is bypassed, so the scope-change and full CIA impact ratings are vendor assertions that cannot be independently verified from the available sources. |
| Exploit ScenarioDerived | A remote attacker who already holds valid low-privilege credentials on an IBM API Connect deployment (12.1.0.0-12.1.1.2) sends requests that cause a trusted internal component to perform privileged actions on the attacker's behalf, bypassing intended security restrictions. Because the CVSS vector is AV:N/AC:L/PR:L/UI:N, no user interaction or elevated privileges are needed beyond initial authentication, and the trigger is not described in the available sources. No public exploit identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 07, 2026
IBM API Connect 12.1.0.0 through 12.1.1.2 contains a confused-deputy weakness that allows an authenticated attacker holding a low-privilege account to bypass security restrictions and have a more trusted component act on their behalf. Successful exploitation is scored at CVSS 9.9 with a scope change and high confidentiality, integrity, and availability impact, meaning the attacker can affect resources beyond the component that granted the original authority; the attack is network-reachable, low complexity, and requires no user interaction, but it does require valid low-privilege credentials (PR:L). IBM has published a fix for the affected range, publicly available exploit code has not been identified at time of analysis, and the precise feature or request path that triggers the confused-deputy behavior is not described in the available sources.
RemediationAI
IBM has released a fix for this issue and the vendor advisory at https://www.ibm.com/support/pages/node/7295635 should be consulted for the exact fixed build to install for your API Connect 12.1.0.0 through 12.1.1.2 deployment; a specific patched version number is not stated in the available data, so confirm the target release on the vendor page before upgrading. The published decision label is act_now, and because the flaw is only reachable with valid low-privilege credentials (PR:L), reducing exposure during the upgrade window means keeping untrusted account provisioning closed and reviewing which low-privilege roles are granted on the instance, since deployments limited to trusted internal users carry materially lower realistic exposure. No public exploit code was identified at time of analysis, but the score of 9.9 with scope change and full confidentiality, integrity, and availability impact warrants prioritizing the vendor fix over workarounds.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-441 (Confused Deputy) describes a design flaw in which a program with greater authority than its caller is tricked into using that authority on behalf of a less-privileged actor, because it fails to verify that the caller is entitled to the operation being requested. In IBM API Connect - an API management product covering gateway, manager, and developer-portal functions - the affected component evidently trusts the context of an authenticated low-privilege session and performs privileged actions without adequately re-validating the requesting user's authorization, which is why the CVSS vector shows PR:L with S:C and uniformly high C/I/A impact. The scope change indicates the impact crosses a trust boundary, so actions taken under the deputy's identity are not confined to the attacker's own privilege domain. The CPE identifier cpe:2.3:a:ibm:api_connect:* confirms the affected product family, with the vendor narrowing the range to versions 12.1.0.0 through 12.1.1.2. The specific API endpoint, module, or protocol path that enables the authorization confusion is not described in the available sources, so the trigger should be treated as unconfirmed rather than assumed to be any particular API or token flow.
Know when Api Connect gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Network-reachable (AV:N) and low-complexity (AC:L) per vendor; PR:L retained because exploitation requires an authenticated account; confused-deputy crossing a trust boundary supports S:C, with impacts as vendor-stated though mechanism is undescribed.
Primary rating from Vendor (ibm).
CVSS VectorNVD
DescriptionNVD
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to bypass security restrictions due to a confused deputy vulnerability.
Executive ViewAI
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a critical confused-deputy vulnerability that enables any user with a low-privilege account to bypass security controls and perform actions as a more trusted component. This puts the integrity and availability of API management infrastructure at risk, potentially exposing sensitive data and disrupting business services. Leadership should prioritize remediation because the flaw is network-reachable, has low attack complexity, and requires no user interaction, making it attractive for attackers with valid credentials.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Api Connect
View allAuthentication bypass in IBM API Connect 10.0.8.0 through 10.0.8.5 and 10.0.11.0 allows remote, unauthenticated attacker
OS command injection in IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 lets a remote attacker
Authenticated code injection in IBM API Connect lets a low-privileged remote user execute arbitrary code by supplying a
Authenticated code execution in IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 lets a remote l
Remote authenticated code execution affects IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2: a
Remote authenticated attackers can execute arbitrary code on IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 thr
Authenticated remote code execution in IBM API Connect 10.0.8.x (10.0.8.0-10.0.8.12) and 12.1.x (12.1.0.0-12.1.1.2) lets
Arbitrary file write via path traversal in IBM API Connect 12.1.0.0 through 12.1.1.2 allows a remote authenticated attac
Privilege escalation in IBM API Connect 10.0.8.x and 12.1.x allows a remote authenticated attacker holding low-privilege
LDAP injection in IBM API Connect (10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2) lets a remote attacker who
SQL injection in IBM API Connect versions 12.1.0.0 through 12.1.1.2 allows a remote, low-privileged authenticated user t
SQL injection in IBM API Connect 12.1.0.0 through 12.1.1.2 allows an authenticated, low-privilege user to execute arbitr
EUVD-2026-118621
GHSA-v94c-jw5j-6c9g
NVD
CVE.org
EPSS
Exploit-DB