CVSS 3.1
5.4 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:LCVE-2026-17114
Medium (5.4) in ibm api connect. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
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 sensitive information and cause a denial of service due to the generation of error messages containing sensitive information.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-209 Generation of Error Message Containing Sensitive Information
- OWASP Top 10
- A10:2025 Mishandling of Exceptional Conditions
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-17114 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-17114?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-17114?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-17114 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-7 Blind SQL Injection Likelihood: High · Severity: High
- CAPEC-54 Query System for Information Likelihood: High · Severity: Low
- CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
- CAPEC-463 Padding Oracle Crypto Attack Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.