Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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-17291 is a high-severity Open Redirect (CWE-601) vulnerability in Ibm Api Connect. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Input Capture (T1056); ranked at the 45th 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 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-118683
Vulnerability Data
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 perform account takeover due to an open redirect vulnerability. The redirect address used during OAuth 2.0 sign-in is not sufficiently validated, which could…
more
allow authentication results to be sent to an attacker-controlled location.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.7.2
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Input validation directly checks and rejects untrusted redirect targets before they are used in a response.
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.
Secure SDLC practices directly require input validation and untrusted-redirect controls that prevent CWE-601.
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.
A.8.29's programme (SAST, code review, vulnerability scanning, penetration testing) reaches open redirects through both SOURCE and RUNTIME: SAST flags redirect calls fed by user input, code review catches unvalidated URL parameters, and pen testing observes the redirect by following crafted URLs. The remainder is bounded and nameable -- conditional or chained redirects, redirects in third-party components not covered by the test plan, and cases where the malicious URL is constructed through non-obvious paths that a single test cycle misses.
A.8.28 mandates secure coding practices (peer review, secure coding standards, training, threat modelling, SAST) that address input validation and redirect handling, so a system under it sees fewer open redirect instances; the practice is fallible and the clause mandates a practice rather than a mechanism, leaving a nameable remainder of instances that slip through, consistent with the A.8.28 -> CWE-502 and A.8.28 -> CWE-79 anchors.
A.8.8's reach is DISCLOSURE — it identifies vulnerabilities through vendor advisories, vulnerability scanning, and tracking third-party libraries. CWE-601 (Open Redirect) does surface as CVEs (CVE-2005-4206, CVE-2008-2951, CVE-2008-2052, CVE-2020-11053), so the disclosed share exists, but open redirects are predominantly a first-party web application code defect, and A.8.8's scanning reaches only the third-party components in its inventory where a published advisory exists — the same logic that graded A.8.8 finds CWE-89 = partial.