Skip to main content
CVE-2026-17369VulnerabilityPublished

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 attacker to force a user

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-17369· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 7 Nov 2026, 08:02 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–
Mavencom.ibm/api_connectpkg:maven/com.ibm/api_connectOther threatsAffected
  • 10.0.8.0 <=10.0.8.12
  • 12.1.0.0 <=12.1.1.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should be cautious of unsolicited authentication requests and consider implementing additional CSRF protections or monitoring authentication flows for anomalies.

Description

IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 contain a cross-site request forgery (CSRF) vulnerability. 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 a login response corresponds to the user's own request, potentially linking the victim's session to the attacker's account.

References

Community reviews

Loading reviews…