Quick answers
- Is CVE-2026-17298 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17298 being exploited in the wild.
- How severe is CVE-2026-17298?
- Critical severity, with a CVSS score of 9.9, published 7 November 2026.
- Which products and versions are affected?
- IBM API Connect 10.0.8.0 through 10.0.8.12, 12.1.0.0 through 12.1.1.2.
- Is there a fix for CVE-2026-17298?
- Yes: fixed in IBM API Connect 10.0.8.13, 12.1.1.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17298 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-17298?
- Check whether you run IBM API Connect at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: IBM API Connect 10.0.8.13, 12.1.1.3
Technical details
Multiple server-side request forgery vulnerabilities exist in IBM API Connect across versions 10.0.8.0–10.0.8.12 and 12.1.0.0–12.1.1.2, requiring an authenticated attacker to craft malicious requests. CVE-2026-17298 specifically allows an authenticated user to make the server contact unintended destinations and retrieve responses; related SSRF flaws (CVE-2026-17237, CVE-2026-17395, CVE-2026-17305, CVE-2026-17384) enable access to internal resources through insufficient validation of user-supplied URLs and request destinations. Fixes are available in version 10.0.8.13 and 12.1.1.3.
Affected products
- IBM API Connect 10.0.8.0 through 10.0.8.12, 12.1.0.0 through 12.1.1.2
Timeline
- 2026-11-07: disclosed