Widely-used enterprise API gateway; auth bypass could disrupt many orgs and draw broad attention.
CVE-2025-13915
Auth bypass in IBM API Connect exposes APIs to unauthorized users.
Is CVE-2025-13915 being exploited?
Not confirmed. CVE-2025-13915 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 9.1% probability of exploitation in the next 30 days.
How severe is CVE-2025-13915?
CVE-2025-13915 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-13915?
Yes. A fix has been recorded for CVE-2025-13915. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-13915 affect?
CVE-2025-13915 affects IBM API Connect 10.0.8.0-10.0.8.5, IBM API Connect 10.0.11.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-13915?
Apply IBM patch ASAP; tighten auth; monitor API activity
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can bypass auth to access APIs and admin features, risking data exposure and config changes.
Immediate action required
- affected>= 10.0.8.0 and <= 10.0.8.5
- affected10.0.11.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.