Skip to main content
VulnerabilityPublished

CVE-2026-17369: IBM API Connect · Cross-Site Request Forgery

Affects IBM API ConnectSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 7 Nov 2026, 05:05 UTC

CVSS 3.1 base score
5.4Medium
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.15.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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
  • >=10.0.8.0 <=10.0.8.12
Fixed in–

CPE configurations (4)

  • cpe:2.3:a:ibm:api_connect:12.1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:12.1.1.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, users should be cautious of unsolicited links or requests that could trigger authentication flows. Implementing anti-CSRF tokens or other request validation mechanisms may mitigate the risk if configurable.

Description

A Cross-Site Request Forgery (CSRF) vulnerability exists in IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2. This flaw allows a remote attacker to trick a user into authenticating into an attacker-controlled account because the sign-in process does not properly verify that the login response matches the user's original request. This could result in the victim's session being linked to the attacker's account.

References

Community reviews

Loading reviews…