Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12893: CWE-295 Improper Certificate Validation in MongoDB Inc. MongoDB Server

0
Medium
VulnerabilityCVE-2025-12893cvecve-2025-12893cwe-295
Published: Tue Nov 25 2025 (11/25/2025, 05:07:17 UTC)
Source: CVE Database V5
Vendor/Project: MongoDB Inc.
Product: 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

AILast updated: 12/02/2025, 06:23:06 UTC

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 improper validation of the Extended Key Usage (EKU) field in TLS client and server certificates during handshake processes on Windows and Apple platforms. Specifically, MongoDB servers on Windows or Apple may accept client certificates that specify extendedKeyUsage but lack the clientAuth attribute, allowing clients to authenticate improperly. Similarly, on Apple platforms, MongoDB servers may establish outbound TLS connections with servers presenting certificates missing the serverAuth EKU attribute. This behavior deviates from the expected strict validation, which is correctly enforced on Linux systems. The vulnerability could allow an attacker to impersonate a legitimate client or server during TLS handshakes, potentially bypassing authentication controls. However, exploitation requires network access and at least low privileges, with no user interaction needed. The vulnerability does not affect availability but may impact confidentiality and integrity to a limited extent. MongoDB Inc. has addressed this issue in patched versions 7.0.26, 8.0.16, and 8.2.2. No public exploits or active exploitation have been reported to date.

Potential Impact

For European organizations, this vulnerability presents a risk primarily to the confidentiality and integrity of data transmitted via TLS connections involving MongoDB servers on Windows and Apple platforms. Attackers could exploit this flaw to impersonate clients or servers, potentially gaining unauthorized access to database services or intercepting sensitive data. This risk is heightened in environments where MongoDB is used for critical applications or stores sensitive personal or business data, such as financial institutions, healthcare providers, and government agencies. The lack of proper EKU validation could undermine trust in TLS authentication, increasing the attack surface for man-in-the-middle or unauthorized access attacks. However, the impact is somewhat limited by the requirement for network access and low privileges, and the absence of user interaction reduces the likelihood of widespread exploitation. Organizations relying on Linux-based MongoDB deployments are not affected. The medium CVSS score reflects these moderate risks. Failure to patch could lead to compliance issues with European data protection regulations like GDPR if unauthorized access or data exposure occurs.

Mitigation Recommendations

European organizations should promptly upgrade MongoDB Server instances running on Windows and Apple platforms to versions 7.0.26, 8.0.16, or 8.2.2 or later to remediate this vulnerability. Until patches are applied, organizations should consider the following mitigations: restrict network access to MongoDB servers using firewall rules and network segmentation to limit exposure; enforce strict client and server certificate issuance policies ensuring proper EKU attributes; implement additional application-layer authentication and authorization controls to reduce reliance solely on TLS client authentication; monitor TLS handshake logs for anomalous certificate usage or unexpected client/server connections; and conduct regular vulnerability scans and penetration tests focusing on TLS configurations. Additionally, organizations should review and update their incident response plans to address potential misuse of TLS authentication flaws. Coordination with certificate authorities to validate EKU attributes in issued certificates can further reduce risk. Finally, educating system administrators and security teams about this specific vulnerability will help ensure timely detection and response.

Need more detailed analysis?Upgrade to Pro Console

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: 12/2/2025, 6:23:06 AM

Last updated: 1/10/2026, 10:12:36 PM

Views: 86

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats