CVE-2025-12893: CWE-295 Improper Certificate Validation in MongoDB Inc. MongoDB Server
Clients may successfully perform a TLS handshake with a MongoDB server despite presenting a client certificate not aligning with the documented Extended Key Usage (EKU) requirements. A certificate that specifies extendedKeyUsage but is missing extendedKeyUsage = clientAuth may still be successfully authenticated via the TLS handshake as a client. This issue is specific to MongoDB servers running on Windows or Apple as the expected validation behavior functions correctly on Linux systems. Additionally, MongoDB servers may successfully establish egress TLS connections with servers that present server certificates not aligning with the documented Extended Key Usage (EKU) requirements. A certificate that specifies extendedKeyUsage but is missing extendedKeyUsage = serverAuth may still be successfully authenticated via the TLS handshake as a server. This issue is specific to MongoDB servers running on Apple as the expected validation behavior functions correctly on both Linux and Windows systems. This vulnerability affects MongoDB Server v7.0 versions prior to 7.0.26, MongoDB Server v8.0 versions prior to 8.0.16 and MongoDB Server v8.2 versions prior to 8.2.2
AI Analysis
Technical Summary
CVE-2025-12893 is a vulnerability classified under CWE-295 (Improper Certificate Validation) affecting MongoDB Server versions 7.0 (before 7.0.26), 8.0 (before 8.0.16), and 8.2 (before 8.2.2). The issue arises from the server's TLS handshake implementation on Windows and Apple platforms, where the validation of client and server certificates does not properly enforce Extended Key Usage (EKU) constraints. Specifically, a client certificate that specifies extendedKeyUsage but lacks the clientAuth EKU can still be accepted by the MongoDB server during TLS client authentication on Windows and Apple. Similarly, on Apple systems, MongoDB servers may accept server certificates missing the serverAuth EKU during outbound TLS connections. This improper validation undermines the trust model of TLS, potentially allowing unauthorized clients to authenticate or enabling man-in-the-middle attacks by accepting improperly validated server certificates. The vulnerability does not affect Linux MongoDB servers, which correctly enforce EKU requirements. The CVSS v3.1 base score is 4.2 (medium), reflecting network attack vector, high attack complexity, low privileges required, no user interaction, and limited confidentiality and integrity impact without availability impact. No known exploits have been reported to date. The vulnerability is particularly relevant for environments where MongoDB servers run on Windows or Apple platforms and rely on strict TLS client and server certificate validation for security.
Potential Impact
For European organizations, this vulnerability could lead to unauthorized access to MongoDB servers or interception of TLS connections if attackers exploit the improper certificate validation. Confidentiality and integrity of data transmitted over TLS may be compromised, especially in environments using client certificate authentication or mutual TLS. Organizations using MongoDB on Windows or Apple platforms are at risk, particularly those in regulated sectors such as finance, healthcare, and government where data protection is critical. Attackers with network access and low privileges could bypass certificate restrictions, potentially gaining unauthorized database access or intercepting sensitive data. Although no availability impact is expected, the breach of confidentiality and integrity could lead to data leaks, compliance violations (e.g., GDPR), and reputational damage. The risk is lower for Linux-based MongoDB deployments, which are not affected. Given the medium severity and absence of known exploits, the immediate risk is moderate but warrants timely remediation to prevent future exploitation.
Mitigation Recommendations
European organizations should promptly upgrade MongoDB Server to versions 7.0.26, 8.0.16, 8.2.2 or later to remediate this vulnerability. Until patches are applied, organizations should enforce strict network segmentation and firewall rules to restrict access to MongoDB servers, limiting exposure to trusted clients and internal networks only. Implement monitoring and alerting for unusual TLS handshake failures or unexpected client certificate usage. Review and tighten TLS configuration policies, ensuring only certificates with proper EKU extensions are issued and trusted within the organization. Consider deploying additional network-level TLS inspection or mutual TLS enforcement mechanisms external to MongoDB to compensate for the validation gap. Conduct audits of existing client and server certificates to verify compliance with EKU requirements. For Apple platform deployments, extra caution is advised due to the broader scope of the issue affecting both client and server certificate validation. Finally, maintain up-to-date asset inventories to identify all MongoDB instances running on affected platforms for prioritized patching.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Belgium, Poland, Switzerland
CVE-2025-12893: CWE-295 Improper Certificate Validation in MongoDB Inc. MongoDB Server
Description
Clients may successfully perform a TLS handshake with a MongoDB server despite presenting a client certificate not aligning with the documented Extended Key Usage (EKU) requirements. A certificate that specifies extendedKeyUsage but is missing extendedKeyUsage = clientAuth may still be successfully authenticated via the TLS handshake as a client. This issue is specific to MongoDB servers running on Windows or Apple as the expected validation behavior functions correctly on Linux systems. Additionally, MongoDB servers may successfully establish egress TLS connections with servers that present server certificates not aligning with the documented Extended Key Usage (EKU) requirements. A certificate that specifies extendedKeyUsage but is missing extendedKeyUsage = serverAuth may still be successfully authenticated via the TLS handshake as a server. This issue is specific to MongoDB servers running on Apple as the expected validation behavior functions correctly on both Linux and Windows systems. This vulnerability affects MongoDB Server v7.0 versions prior to 7.0.26, MongoDB Server v8.0 versions prior to 8.0.16 and MongoDB Server v8.2 versions prior to 8.2.2
AI-Powered Analysis
Technical Analysis
CVE-2025-12893 is a vulnerability classified under CWE-295 (Improper Certificate Validation) affecting MongoDB Server versions 7.0 (before 7.0.26), 8.0 (before 8.0.16), and 8.2 (before 8.2.2). The issue arises from the server's TLS handshake implementation on Windows and Apple platforms, where the validation of client and server certificates does not properly enforce Extended Key Usage (EKU) constraints. Specifically, a client certificate that specifies extendedKeyUsage but lacks the clientAuth EKU can still be accepted by the MongoDB server during TLS client authentication on Windows and Apple. Similarly, on Apple systems, MongoDB servers may accept server certificates missing the serverAuth EKU during outbound TLS connections. This improper validation undermines the trust model of TLS, potentially allowing unauthorized clients to authenticate or enabling man-in-the-middle attacks by accepting improperly validated server certificates. The vulnerability does not affect Linux MongoDB servers, which correctly enforce EKU requirements. The CVSS v3.1 base score is 4.2 (medium), reflecting network attack vector, high attack complexity, low privileges required, no user interaction, and limited confidentiality and integrity impact without availability impact. No known exploits have been reported to date. The vulnerability is particularly relevant for environments where MongoDB servers run on Windows or Apple platforms and rely on strict TLS client and server certificate validation for security.
Potential Impact
For European organizations, this vulnerability could lead to unauthorized access to MongoDB servers or interception of TLS connections if attackers exploit the improper certificate validation. Confidentiality and integrity of data transmitted over TLS may be compromised, especially in environments using client certificate authentication or mutual TLS. Organizations using MongoDB on Windows or Apple platforms are at risk, particularly those in regulated sectors such as finance, healthcare, and government where data protection is critical. Attackers with network access and low privileges could bypass certificate restrictions, potentially gaining unauthorized database access or intercepting sensitive data. Although no availability impact is expected, the breach of confidentiality and integrity could lead to data leaks, compliance violations (e.g., GDPR), and reputational damage. The risk is lower for Linux-based MongoDB deployments, which are not affected. Given the medium severity and absence of known exploits, the immediate risk is moderate but warrants timely remediation to prevent future exploitation.
Mitigation Recommendations
European organizations should promptly upgrade MongoDB Server to versions 7.0.26, 8.0.16, 8.2.2 or later to remediate this vulnerability. Until patches are applied, organizations should enforce strict network segmentation and firewall rules to restrict access to MongoDB servers, limiting exposure to trusted clients and internal networks only. Implement monitoring and alerting for unusual TLS handshake failures or unexpected client certificate usage. Review and tighten TLS configuration policies, ensuring only certificates with proper EKU extensions are issued and trusted within the organization. Consider deploying additional network-level TLS inspection or mutual TLS enforcement mechanisms external to MongoDB to compensate for the validation gap. Conduct audits of existing client and server certificates to verify compliance with EKU requirements. For Apple platform deployments, extra caution is advised due to the broader scope of the issue affecting both client and server certificate validation. Finally, maintain up-to-date asset inventories to identify all MongoDB instances running on affected platforms for prioritized patching.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mongodb
- Date Reserved
- 2025-11-07T18:24:11.002Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69253b14441560fe7ee1e752
Added to database: 11/25/2025, 5:13:56 AM
Last enriched: 11/25/2025, 5:28:52 AM
Last updated: 11/25/2025, 6:16:40 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-13644: CWE-617: Reachable Assertion in MongoDB Inc. MongoDB Server
MediumCVE-2025-12742: CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in Google Cloud Looker
HighCVE-2025-13643: CWE-862: Missing Authorization in MongoDB Inc. MongoDB Server
LowCVE-2025-64730: Cross-site scripting (XSS) in Sony Corporation SNC-CX600W
MediumCVE-2025-62497: Cross-site request forgery (CSRF) in Sony Corporation SNC-CX600W
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.