CVSS 3.1
6.4 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NCVE-2026-17370 Multiple Vulnerabilities in IBM API Connect
Medium (6.4) in ibm api connect. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
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 obtain an access token for another user due to improper authentication. The sign-in flow does not sufficiently verify the identity of the user completing it, which could allow another user's identity to be assumed.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-13. 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-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-287 Improper Authentication
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- Assigned by
- ibm (CNA)
- NVD analysis
- Under analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-17370 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-17370?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-17370?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-17370 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.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-17370)
HTML:
<a href="https://cve.bz/cve/CVE-2026-17370"><img src="https://cve.bz/cve/badge/CVE-2026-17370.svg" alt="CVE-2026-17370"></a>
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-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-114 Authentication Abuse Severity: Medium
- CAPEC-115 Authentication Bypass Severity: Medium
- CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
- CAPEC-194 Fake the Source of Data Severity: Medium
- CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
- CAPEC-633 Token Impersonation Severity: Medium
- CAPEC-650 Upload a Web Shell to a Web Server Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.