CVE-2025-13915: IBM API Connect · Authentication Bypass by Primary Weakness
Affects IBM API ConnectSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 9.0% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM API Connect | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-13915, organizations should prioritize the following actions: 1) Monitor IBM’s official channels closely for the release of security patches addressing this vulnerability and apply them immediately upon availability. 2) Implement network-level access controls to restrict access to the API Connect management interfaces, limiting exposure to trusted IP addresses and internal networks only. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block anomalous requests that may attempt to exploit authentication bypass. 4) Conduct thorough audits of API Connect logs to identify any unauthorized access attempts or suspicious activities. 5) Enforce multi-factor authentication (MFA) on all administrative access points where possible to add an additional security layer. 6) Segment API Connect infrastructure from other critical systems to contain potential breaches. 7) Develop and test incident response plans specifically for API platform compromises. 8) Educate security teams about this vulnerability to ensure rapid detection and response. These targeted mitigations, combined with prompt patching, will significantly reduce the risk posed by this critical authentication bypass flaw.
Description
IBM API Connect 10.0.8.0 through 10.0.8.5, and 10.0.11.0 could allow a remote attacker to bypass authentication mechanisms and gain unauthorized access to the application.