CVE-2025-9312
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWSO2 products contain a missing authentication enforcement vulnerability in their mTLS implementation for System REST APIs and SOAP services. Due to improper validation of client certificate-based authentication in certain default configurations, affected components accept requests without enforcing mTLS authentication when relying on default settings or when the mTLS authenticator is enabled for SOAP services. This allows unauthenticated attackers with network access to gain administrative privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.5.0= 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= 5.2.0= 5.3.0= 5.4.0= 5.4.1= 5.5.0= 5.6.0= 5.7.0= 5.8.0= 5.9.0= 5.10.0= 5.11.0= 6.0.0= 5.3.0= 5.5.0= 5.6.0= 5.7.0= 5.9.0= 5.10.0= 1.4.0= 1.5.0= 2.0.0= 2.0.0= 1.4.0= 1.5.0= 4.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WSO2 product and versionLocate the product version file (typically in PRODUCT_HOME/repository/conf/version.properties or check the product banner on startup). Common products: API Manager, Identity Server, Identity Server as Key Manager, Open Banking AM/IAM/KM, Traffic Manager.Affected if The installed product matches one of the affected products AND version numbers listed in the CVE (e.g., API Manager 2.2.0-4.4.0, Identity Server 5.2.0-6.0.0, etc.)
-
Check if mTLS is enabled for System REST APIsExamine the deployment.toml file (repository/conf/deployment.toml) for the [apim.mtls] or [transport.mtls] section. Look for settings like 'enabled=true' under mTLS configuration for API manager components, or check carbon.xml for transport receiver settings that accept client certificates.Affected if mTLS is enabled for System REST APIs and the configuration relies on default settings without proper client certificate validation enforcement
-
Verify SOAP service mTLS authenticator configurationCheck the deployment.toml or carbon.xml for the mTLS authenticator configuration. Look for 'Authenticator' or 'MTLSAuthenticator' entries in the authenticators section, particularly for SOAP-based services.Affected if The mTLS authenticator is enabled for SOAP services and accepts requests without enforcing proper client certificate validation
-
Inspect transport-level mTLS settingsReview the transport receiver configurations in the deployment.toml or axis2/axis2.xml for HTTPS listeners. Check for 'trustStore' settings and verify if 'verifyClient' or 'clientAuth' is properly set to 'require' or 'verify' rather than 'allow' or 'none'.Affected if Transport listeners accept client certificates but do not require them (clientAuth set to 'allow' or not explicitly set to 'require')
You are affected if you run a listed WSO2 product version AND have mTLS enabled for System REST APIs or SOAP services using default configurations that do not enforce mandatory client certificate validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReview and enforce proper mTLS authentication configuration for System REST APIs and SOAP services, or disable the affected mTLS flows if not required. Ensure client certificate validation is properly enforced rather than relying on default settings.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9312 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data