Skip to main content

IBM API Connect CVE-2025-13915

CRITICAL
Authentication Bypass by Primary Weakness (CWE-305)
2025-12-26 psirt@us.ibm.com
9.8
CVSS 3.1 · Vendor: us
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed API Connect endpoint
  2. Exploit
    Send crafted request bypassing auth
  3. Execution
    Gain unauthorized application access
  4. Impact
    Read/modify protected API resources

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Primary weakness mitigation
Exploitation Conditions

No special conditions stated - the description and CVSS vector (AV:N/AC:L/PR:N/UI:N) indicate remote unauthenticated exploitation of IBM API Connect against default reachable deployments. The primary limiting factor is version scope: only IBM API Connect 10.0.8.0 through 10.0.8.5 and 10.0.11.0 are listed as affected, so instances outside these versions are not exposed to this specific flaw. Network reachability to the API Connect management/gateway interface is the practical prerequisite; the description names no feature toggle, non-default setting, or deployment mode required to trigger the bypass.

Impact

The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8 Critical) describes a network-reachable, low-complexity, unauthenticated authentication bypass with full confidentiality, integrity, and availability impact on IBM API Connect - the worst-case profile for a severity score. The CWE-305 classification and 'Authentication Bypass' tag are consistent with the description, so the vulnerability class itself is coherent and not a case of inflated CVSS. However, the real-world-risk signals that normally sharpen prioritization are entirely absent from the input: no EPSS exploitation-probability score is provided, the vulnerability is not indicated as being on the CISA KEV list, and no proof-of-concept is referenced (the single reference is the IBM vendor advisory node 7255149). Per the precision rules this means 'no public exploit identified at time of analysis.' There is no SSVC decision data supplied either. Net assessment: this is a genuine high-priority patch candidate because an unauthenticated auth bypass on an internet-facing API gateway is exactly the kind of flaw that gets weaponized quickly, but the absence of EPSS/KEV/POC evidence means active exploitation cannot be claimed - treat it as high-urgency-by-nature rather than high-urgency-by-confirmed-exploitation. No conflicting signals were found between the CVSS vector and the description; both agree on remote unauthenticated access.

Exploit ScenarioDerived

A remote attacker with network reach to an exposed IBM API Connect instance (versions 10.0.8.0-10.0.8.5 or 10.0.11.0) sends requests that bypass the authentication layer, obtaining unauthorized access to the application without valid credentials. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no authentication, user interaction, or special timing is needed. No public exploit code is identified at time of analysis, so exploitation would require the attacker to independently develop the bypass technique.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 9.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Authentication bypass in IBM API Connect 10.0.8.0 through 10.0.8.5 and 10.0.11.0 allows remote, unauthenticated attackers to gain unauthorized access with full confidentiality, integrity, and availability impact, as reflected by a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The flaw is a CWE-305 primary authentication weakness that requires only network reachability to the affected management or gateway interface, with no user interaction or special conditions. No public exploit code has been identified at time of analysis, and no KEV entry is present; affected organizations should refer to IBM's advisory at https://www.ibm.com/support/pages/node/7255149 for mitigation guidance.

RemediationAI

No vendor-released patch version is provided in the available data; consult IBM's advisory at https://www.ibm.com/support/pages/node/7255149 for the exact fix or upgrade path. Until a patch is applied, the primary compensating control is to restrict network access to the IBM API Connect management and gateway interfaces to trusted networks, for example by using firewall rules, VPNs, or network segmentation; this may limit legitimate administrative access but directly reduces exposure to the unauthenticated network attack. Additionally, enable and monitor authentication logs for anomalous access attempts, and enforce multi-factor authentication where supported, though these are detective rather than preventive. If the affected component is not strictly necessary, consider temporarily disabling it or removing it from network exposure, accepting the associated loss of API management functionality. Monitor IBM's advisory for updated remediation guidance.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

IBM API Connect is an API management platform that provides management, gateway, and analytics components, and the vulnerability resides in its authentication mechanism. The root cause is CWE-305 Authentication Bypass by Primary Weakness, meaning the authentication design itself can be bypassed, allowing an attacker to authenticate without valid credentials. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H indicates the bypass is exploitable over the network (AV:N) with low complexity (AC:L) and no privileges (PR:N) or user interaction (UI:N), resulting in high confidentiality, integrity, and availability impact. Affected CPEs are cpe:2.3:a:ibm:api_connect:*:*:*:*:*:*:*:* and cpe:2.3:a:ibm:api_connect:10.0.11.0:*:*:*:*:*:*:*, aligning with the described version range of 10.0.8.0-10.0.8.5 and 10.0.11.0. No additional prerequisites, feature toggles, or non-default settings are stated in the available intelligence, making any network-reachable deployment of the affected versions a potential target.

Know when Api Connect gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (us) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

An unauthenticated remote authentication bypass is network-reachable with no privileges or interaction (AV:N/AC:L/PR:N/UI:N), and unauthorized application access plausibly yields full C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (us).

CVSS VectorVendor: us

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

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

IBM API Connect versions 10.0.8.0 through 10.0.8.5 and 10.0.11.0 are affected by a critical authentication bypass (CVE-2025-13915) that allows remote, unauthenticated attackers to gain full control over API management interfaces. This vulnerability poses a severe risk to organizations relying on these versions for API security, potentially leading to data breaches, service disruption, and regulatory non-compliance. Leadership should prioritize immediate mitigation because the flaw requires no authentication and can be exploited remotely, and no public exploit identified at time of analysis.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include network segmentation, IP allowlisting for management and gateway interfaces, deployment of an authenticating reverse proxy, and enhanced monitoring for unauthorized access attempts. Refer to IBM advisory at https://www.ibm.com/support/pages/node/7255149 for further guidance.

Threat Intelligence Overview

EPSS Score
9.0%
Top 5% exploitable
Prevalence
Medium
enterprise API management gateway, significant but not universal footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 9.0%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

58
Low Medium High Critical
KEV: 0
EPSS: +9
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Affected Products (CPE)CVE.org

cpe:2.3:a:ibm:api_connect:*:*:*:*:*:*:*:*
cpe:2.3:a:ibm:api_connect:10.0.11.0:*:*:*:*:*:*:*
CVE-2019-4202 CRITICAL
10.0 Apr 15

IBM API Connect 5.0.0.0 and 5.0.8.6 Developer Portal is vulnerable to command injection. Rated critical severity (CVSS 1

CVE-2018-1789 CRITICAL
9.9 Sep 07

IBM API Connect v2018.1.0 through v2018.3.4 could allow an attacker to send a specially crafted request to conduct a ser

CVE-2018-1712 CRITICAL
9.9 Aug 16

IBM API Connect's Developer Portal 5.0.0.0 through 5.0.8.3 is vulnerable to Server Side Request Forgery. Rated critical

CVE-2026-9074 CRITICAL
9.8 Jul 08

Unauthenticated SQL injection in IBM API Connect's password reset functionality allows remote attackers to inject arbitr

CVE-2026-3144 CRITICAL
9.8 Jul 08

Authentication bypass via default credentials in IBM API Connect 12.1.0.0 through 12.1.0.3 lets remote unauthenticated a

CVE-2021-29772 CRITICAL
9.8 Aug 26

IBM API Connect 5.0.0.0 through 5.0.8.11 could allow a user to potentially inject code due to unsanitized user input. Ra

CVE-2019-4203 CRITICAL
9.8 Apr 15

IBM API Connect 5.0.0.0 and 5.0.8.6 Developer Portal can be exploited by app developers to download arbitrary files from

CVE-2019-4155 CRITICAL
9.8 Apr 08

IBM API Connect's Developer Portal 2018.1 and 2018.4.1.3 is impacted by a privilege escalation vulnerability when integr

CVE-2019-4008 CRITICAL
9.8 Feb 07

API Connect V2018.1 through 2018.4.1.1 is impacted by access token leak. Rated critical severity (CVSS 9.8), this vulner

CVE-2018-1784 CRITICAL
9.8 Dec 20

IBM API Connect 5.0.0.0 and 5.0.8.4 is affected by a NoSQL Injection in MongoDB connector for the LoopBack framework. Ra

CVE-2018-1469 CRITICAL
9.8 Apr 04

IBM API Connect Developer Portal 5.0.0.0 through 5.0.8.2 could allow an unauthenticated attacker to execute system comma

CVE-2021-29715 CRITICAL
9.1 Aug 26

IBM API Connect 5.0.0.0 through 5.0.8.11 could alllow a remote user to obtain sensitive information or conduct denial of

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy