Skip to main content

IBM API Connect CVE-2026-17342

| EUVDEUVD-2026-118733 CRITICAL
Code Injection (CWE-94)
2026-11-07 ibm GHSA-2rp4-2ccx-c669
9.9
CVSS 3.1 · Vendor: ibm
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privileged account
  2. Delivery
    Submit crafted input to vulnerable interface
  3. Exploit
    Trigger improper code generation (CWE-94)
  4. Execution
    Execute arbitrary code on server
  5. Impact
    Cross scope to impact other resources

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a valid authenticated session on the target IBM API Connect instance (CVSS PR:L indicates low-privileged authentication is needed, not an anonymous attacker), but no user interaction and no special network positioning (AV:N/UI:N). The affected deployments are IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2; versions outside these ranges and patched instances are not affected. The limiting factor is the authentication requirement - an attacker must first obtain or be granted a low-privilege account - which reduces exposure for instances that tightly control account provisioning. The specific product feature, API, or configuration that performs the vulnerable code generation is not identified in the available sources, so the exact triggering surface cannot be named.

Impact

This is a genuine high-priority issue, not a CVSS-inflated one. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, 9.9) describes network-reachable exploitation of low complexity requiring only low-level privileges (PR:L = an authenticated but non-administrative user), with no user interaction and a scope change (S:C) yielding total confidentiality, integrity, and availability impact - consistent with CWE-94 code injection leading to arbitrary code execution. The vuln.today Decision label is act_now and IBM has shipped a patch, which together argue for prompt remediation. However, the exploitation signals are mixed and partly absent: no EPSS probability was provided, the CVE is not listed in CISA KEV in this input, and no PoC or exploit reference is present - so there is no evidence of active exploitation or public exploit code at this time. The prioritization therefore rests on the severe technical impact and low attack prerequisites (any authenticated account suffices) rather than on observed in-the-wild activity. The scope change (S:C) implies the vulnerable component can impact resources beyond its own security scope; the description does not detail the mechanism, so the exact privilege boundary crossed is not confirmed from available data.

Exploit ScenarioDerived

A remote attacker who already holds a low-privileged authenticated account on an affected IBM API Connect instance (10.0.8.0-10.0.8.12 or 12.1.0.0-12.1.1.2) submits crafted input that the platform improperly incorporates into generated code, causing arbitrary code execution on the server. Because the CVSS vector is AV:N/AC:L/PR:L/UI:N with a scope change, no victim interaction is needed and the impact can extend beyond the initial component. No public exploit identified at time of analysis, so this scenario is inferred from the CVSS metrics and CWE-94 classification rather than from a demonstrated exploit.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.9% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 07, 2026

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 low-privileged user run arbitrary code on the application server, and the independent assessment rates it a genuine high-priority issue rather than CVSS inflation. The CVSS 3.1 score is 9.9 with scope change (S:C) and CWE-94 improper control of code generation; exploitation requires a valid authenticated session (PR:L) but no user interaction. No public exploit has been identified at time of analysis and there is no KEV entry, while IBM has published vendor patches and the decision label is act_now.

RemediationAI

IBM's patch status is available from vendor; consult the IBM support pages at https://www.ibm.com/support/pages/node/7295635 and https://www.ibm.com/support/pages/node/7295637 to identify and apply the fixed release for the affected 10.0.8.x or 12.1.x branch. Because exploitation requires a valid authenticated session with low privileges (PR:L), a practical compensating control until patching is complete is to tighten account provisioning and review low-privileged accounts on exposed API Connect instances; the trade-off is reduced operational flexibility for API developers and administrators who rely on those accounts. The exact feature, API, or endpoint that must be restricted is not identified in the available sources, so no specific endpoint-level workaround can be prescribed from this data.

Affected VersionsENISA

API Connect 12.1.0.0 ≤12.1.1.2
API Connect 10.0.8.0 ≤10.0.8.12

Affected Packages

euvd api_connect no fix

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

IBM API Connect is an API management platform, and CVE-2026-17342 is classified under CWE-94, improper control of generation of code, which is the code-injection class where attacker-influenced input reaches code-generation logic without adequate restriction. The CVSS vector indicates network reachability, low attack complexity, low privileges, no user interaction, and scope change, meaning the vulnerable component may affect resources beyond its own security scope. The specific product feature, API, or configuration that performs the vulnerable code generation is not identified in the available sources, so the exact triggering surface cannot be named. The CPE cpe:2.3:a:ibm:api_connect:*:*:*:*:*:*:*:* is a wildcard and must be resolved against the IBM advisory; ENISA EUVD-2026-118733 lists the affected ranges as API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2.

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

Vendor (ibm) PRIMARY 9.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.9 CRITICAL

Network-reachable code injection needing only a low-privileged account (PR:L), no interaction, with arbitrary code execution and scope change (S:C) giving full C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary code due to improper control of generation of code.

Executive ViewAI

Why It Matters

IBM API Connect, a critical platform for API management and integration, contains a code execution vulnerability (CVE-2026-17342) that allows authenticated low-privileged users to run arbitrary code on the application server. This compromises the confidentiality, integrity, and availability of the API infrastructure, potentially exposing sensitive business data and disrupting digital services. Leadership should prioritize remediation given the critical severity and the product's role in enabling business operations.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.9%
Top 42% exploitable
Prevalence
Medium
enterprise API management gateway, common in large orgs but not ubiquitous
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.9%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2025-13915 CRITICAL
9.8 Dec 26

Authentication bypass in IBM API Connect 10.0.8.0 through 10.0.8.5 and 10.0.11.0 allows remote, unauthenticated attacker

CVE-2026-17402 CRITICAL
9.9 Nov 07

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

CVE-2026-17359 CRITICAL
9.9 Nov 07

Authenticated code injection in IBM API Connect lets a low-privileged remote user execute arbitrary code by supplying a

CVE-2026-17117 CRITICAL
9.9 Nov 07

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

CVE-2026-17399 CRITICAL
9.9 Nov 07

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

CVE-2026-17150 CRITICAL
9.9 Nov 07

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

CVE-2026-17354 CRITICAL
9.9 Nov 07

Arbitrary file write via path traversal in IBM API Connect 12.1.0.0 through 12.1.1.2 allows a remote authenticated attac

CVE-2026-17158 CRITICAL
9.9 Nov 07

Privilege escalation in IBM API Connect 10.0.8.x and 12.1.x allows a remote authenticated attacker holding low-privilege

CVE-2026-17392 CRITICAL
9.9 Nov 07

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

CVE-2026-17336 CRITICAL
9.9 Nov 07

SQL injection in IBM API Connect versions 12.1.0.0 through 12.1.1.2 allows a remote, low-privileged authenticated user t

CVE-2026-17132 CRITICAL
9.9 Nov 07

SQL injection in IBM API Connect 12.1.0.0 through 12.1.1.2 allows an authenticated, low-privilege user to execute arbitr

CVE-2026-17049 CRITICAL
9.9 Nov 07

IBM API Connect 12.1.0.0 through 12.1.1.2 let a remote, authenticated user with only low privileges read sensitive infor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy