Clients may successfully perform a TLS handshake with a MongoDB server despite presenting a client certificate not
Source GCVE Database
Not known to be exploited · CVSS 4.2 Medium · fixed in 8.2.2 : update affected systems when convenient.
Data as of 18 Nov 2026, 02:28 UTC
Thin evidence
One scorer or none| CNA (mongodb) | CVSS 3.1 | 4.2 |
|---|---|---|
| CNA (mongodb) | CVSS 4.0 | 2.3 |
- 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
Weaponized: 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 17 Nov 2026.
What to do
AI-suggested
Fixed versions are available: MongoDB Server v7.0.26, v8.0.16, and v8.2.2 address this issue. Users should upgrade affected MongoDB Server instances to these or later versions to ensure proper EKU validation during TLS handshakes. No additional mitigations are specified.
Description
MongoDB servers running on Windows or Apple platforms may accept client certificates during TLS handshake even if those certificates lack the required Extended Key Usage (EKU) for client authentication. Similarly, MongoDB servers on Apple platforms may accept server certificates for egress TLS connections without the required EKU for server authentication. This behavior deviates from the expected validation and affects MongoDB Server versions prior to 7.0.26, 8.0.16, and 8.2.2.