Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-17331 is a high-severity External Control of File Name or Path (CWE-73) vulnerability in Ibm (inferred from references). Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Office Test (T1137.002); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-118722
Vulnerability Data
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to read arbitrary files on the server due to external control of a file name or path.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Enforces authorization checks on the actual resource accessed, blocking unauthorized files even when a malicious path is supplied.
Input validation directly rejects or sanitizes untrusted path strings before they reach filesystem operations.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect path-traversal issues but does not itself implement preventive controls.
Training developers about input validation and path handling reduces instances of CWE-73 but is fallible human practice; the weakness is a code-level implementation defect that training alone cannot fully prevent, leaving a nameable remainder of cases where developers still write unvalidated path operations.
Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces ordinary software weaknesses like CWE-73 in delivered code the way those practices do, at partial -- the same reading the owner applied to A.8.30 vs CWE-134.
A.8.8's reach is DISCLOSURE-based: it finds CWE-73 where the weakness surfaces as a published advisory in a third-party component (CVE-2022-45918, CVE-2008-5748, CVE-2008-5764 are examples), but the bulk of CWE-73 instances live in first-party code where static analysis and code review — A.8.29's territory — are the High-rated detection methods, leaving the disclosed share a minority.