CVE-2025-12893

Improper Certificate Validation May Allow Successful TLS Handshaking Despite Invalid Extended Key Usage Fields in MongoDB Server

MEDIUM
5.4
CVSS Score
Published: November 25, 2025 at 05:07 AM UTC
Updated: October 18, 2026 at 08:10 PM UTC
1 product affected across 1 vendorMongoDB

Using MongoDB Server by MongoDB Inc.?

Get instant alerts when new vulnerabilities affect MongoDB Server - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.4
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions7.0.0 ≤ v < 7.0.268.0.0 ≤ v < 8.0.168.2.0 ≤ v < 8.2.27.08.08.2
Affected range stops below 7.0.26, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

Vendor Advisory
Source: cverecord
https://jira.mongodb.org/browse/SERVER-105783

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-295

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card