Skip to main content
VulnerabilityPublished

CVE-2026-17344: IBM API Connect · Server-Side Request Forgery

Affects IBM API ConnectSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 7 Nov 2026, 05:17 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (ibm)CVSS 3.19.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
IBMAPI ConnectAffected
  • >=12.1.0.0 <=12.1.1.2
Fixed in–

CPE configurations (2)

  • cpe:2.3:a:ibm:api_connect:12.1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:12.1.1.2:*:*:*:*:*:*:*

AI-suggested

Until a fix is available, restrict network access to the vulnerable service and monitor for unusual request patterns to mitigate exploitation risk.

Description

IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a server-side request forgery (SSRF) vulnerability that allows a remote attacker to cause the service to send requests to unintended destinations. This vulnerability can be exploited without authentication and may lead to the exposure of sensitive information.

References

Community reviews

Loading reviews…