CVE-2026-17384: IBM API Connect · Server-Side Request Forgery
Affects IBM API ConnectSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 7 Nov 2026, 05:53 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 8.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMAPI Connect | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:ibm:api_connect:10.0.8.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:api_connect:10.0.8.12:*:*:*:*:*:*:*
AI-suggested
Until a fix is available, restrict access to the affected versions and monitor for updates from IBM. Since this vulnerability requires authentication, enforcing strong access controls and limiting user privileges may reduce risk.
Description
IBM API Connect versions 10.0.8.0 through 10.0.8.12 contain a server-side request forgery (SSRF) vulnerability that allows a remote authenticated attacker to obtain sensitive information. The vulnerability is identified as CWE-918 and has a high severity score of 8.5. It requires low attack complexity and no user interaction but does require privileges to authenticate. The flaw impacts confidentiality significantly but has limited impact on integrity and no impact on availability.