CVE-2026-17312VulnerabilityPublished 7 Nov 2026

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to force a user to authenticate into an

Source GCVE Database

Compare

Authoritative record:CVE-2026-17312· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 7 Nov 2026, 08:04 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.1	5.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-v94h-g9fm-f24x

What to do

Affected software

Product	Affected	Fixed in
IBMAPI Connect	Affected >=12.1.0.0 <=12.1.1.2	Fixed in–

AI-suggested

Since the vulnerability is published and affects specific versions, users should monitor IBM's official advisories for patches or updates. Until a fix is available, users should consider implementing CSRF protections such as anti-CSRF tokens or other application-layer mitigations to prevent exploitation.

Description

IBM API Connect versions 12.1.0.0 through 12.1.1.2 are vulnerable to a cross-site request forgery (CSRF) issue that could allow a remote attacker to force a user to authenticate into an attacker-controlled account. The vulnerability arises because the sign-in flow does not properly verify that a login response corresponds to the user's own authentication request, potentially linking the victim's session to the attacker's account.

Impact

Successful exploitation could result in a user unknowingly authenticating into an attacker-controlled account, which may lead to session confusion and potential unauthorized actions performed under the victim's session context. The confidentiality and integrity impacts are limited (low), and availability is not affected. The CVSS score of 5.4 (medium severity) reflects the moderate risk posed by this vulnerability.

Summary

This vulnerability in IBM API Connect 12.1.0.0 through 12.1.1.2 involves insufficient verification in the sign-in flow, enabling a remote attacker to exploit cross-site request forgery (CWE-352). By leveraging this flaw, an attacker can cause a user to authenticate into an account controlled by the attacker, effectively hijacking the user's session context. The issue is due to the login response not being adequately bound to the user's original authentication request.

CWE-352Cross-Site Request Forgery (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Nov 2026, 08:04 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats