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 and access sensitive information from other tenants due to insufficient input validation. Uploaded custom module content is not sufficiently validated before it is processed, which could allow code to run with access beyond the user's own tenant.
Severity
CVSS 3.1
9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.8% estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-17150 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-17150?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-17150?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-17150 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
ibm:api connect
Versions
From the CNA's record in the CVE List.
Product
Affected
IBM API Connect
from 12.1.0.0 through 12.1.1.2
IBM API Connect
from 10.0.8.0 through 10.0.8.12
Attack patterns (CAPEC)
CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
CAPEC-6 Argument Injection Likelihood: High · Severity: High
CAPEC-15 Command Delimiters Likelihood: High · Severity: High
CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
CAPEC-182 Flash Injection Likelihood: High · Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.