CVE-2025-12893: MongoDB Server · Improper Certificate Validation
Affects MongoDB ServerSource CVE Database V5
Not known to be exploited · CVSS 4.2 Medium · fixed in 8.2.2 : update MongoDB Server when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.2.2, 8.0.16, 7.0.26
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade MongoDB Server to 8.2.2, 8.0.16 or 7.0.26.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDB Inc. MongoDB Server | Affected
| Fixed in
|
AI-suggested
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. If you cannot patch yet, 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.
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