Skip to main content
CVE-2025-9312VulnerabilityPublished

CVE-2025-9312: WSO2 API Manager · Missing Authentication

Affects WSO2 API ManagerSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.wso2/wso2-api-managerpkg:maven/org.wso2/wso2-api-managerOther threatsAffected
  • =2.2.0
  • =2.5.0
  • =2.6.0
  • =3.0.0
  • =3.1.0
  • =3.2.0
  • =3.2.1
  • =4.0.0
  • =4.1.0
  • =4.2.0
  • =4.3.0
  • =4.4.0
  • =4.5.0
Fixed in–

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

AI-suggested

European organizations should take the following specific actions to mitigate CVE-2025-9312: 1) Immediately audit all WSO2 API Manager deployments to identify usage of System REST APIs and SOAP services with mTLS enabled, focusing on default configurations. 2) Disable or restrict access to the affected mTLS flows if they are not essential to operations. 3) Apply any available patches or updates from WSO2 as soon as they are released; if patches are not yet available, implement compensating controls such as network segmentation and strict firewall rules to limit access to vulnerable endpoints. 4) Enforce additional authentication mechanisms beyond mTLS where possible, such as OAuth or X.509 login flows, which are not affected by this vulnerability. 5) Monitor network traffic and logs for unusual access patterns or unauthorized administrative actions on the API Manager. 6) Conduct penetration testing and vulnerability scanning focused on mTLS configurations to verify the absence of unauthorized access. 7) Educate system administrators and security teams about the vulnerability and ensure secure configuration best practices are followed. 8) Consider deploying Web Application Firewalls (WAFs) or API security gateways that can provide additional authentication and access control layers. These measures, combined with timely patching, will reduce the risk of exploitation and limit potential damage.

Description

A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products. Due to improper validation of client certificate–based authentication in certain default configurations, the affected components may permit unauthenticated requests even when mTLS is enabled. This condition occurs when relying on the default mTLS settings for System REST APIs or when the mTLS authenticator is enabled for SOAP services, causing these interfaces to accept requests without enforcing additional authentication. Successful exploitation allows a malicious actor with network access to the affected endpoints to gain administrative privileges and perform unauthorized operations. The vulnerability is exploitable only when the impacted mTLS flows are enabled and accessible in a given deployment. Other certificate-based authentication mechanisms such as Mutual TLS OAuth client authentication and X.509 login flows are not affected, and APIs served through the API Gateway of WSO2 API Manager remain unaffected.

References

Community reviews

Loading reviews…