dbcve.org
MongoDBDatabase / datastore

CVE-2025-12893

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-25
Fix available
A fix is available. Upgrade to 7.0.26 / 8.0.16 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MongoDB Server fails to properly validate Extended Key Usage (EKU) fields in TLS certificates on Windows and Apple platforms. Client certificates missing 'clientAuth' can authenticate on Windows/Apple (correct on Linux), and server certificates missing 'serverAuth' can authenticate on Apple only (correct on Linux/Windows). This allows connections with certificates that don't meet documented EKU requirements.

MitigationUpgrade MongoDB Server to v7.0.26+, v8.0.16+, or v8.2.2+ to resolve the EKU validation bypass. Alternatively, enforce strict certificate validation via configuration until patching is feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MongoDBDatabase / datastore
Affected:>= 7.0.0, < 7.0.26>= 8.0.0, < 8.0.16>= 8.2.0, < 8.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed MongoDB version
    Run 'db.version()' in mongosh or 'mongod --version' in terminal
    Affected if Version is 7.0.0-7.0.25, 8.0.0-8.0.15, or 8.2.0-8.2.1 (not 7.0.26+, 8.0.16+, or 8.2.2+)

If MongoDB version is in the affected range AND the operating system is Windows or macOS AND TLS authentication with certificates is in use, the environment is vulnerable to EKU validation bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.26 / 8.0.16 / 8.2.2 or later
Fixed in 7.0.268.0.168.2.2
Interim mitigation

Upgrade MongoDB Server to v7.0.26+, v8.0.16+, or v8.2.2+ to resolve the EKU validation bypass. Alternatively, enforce strict certificate validation via configuration until patching is feasible.

Recommended fix High confidence

Upgrade to MongoDB Server 7.0.26, 8.0.16, or 8.2.2 depending on your current major version branch

  1. 1. Identify the currently running MongoDB version by running 'db.version()' in the mongosh shell or checking the MongoDB service version
  2. 2. Stop the MongoDB service or cluster before performing the upgrade
  3. 3. Create a complete backup of all MongoDB data directories and configuration files
  4. 4. For MongoDB 7.0.x versions: Upgrade to version 7.0.26
  5. 5. For MongoDB 8.0.x versions: Upgrade to version 8.0.16
  6. 6. For MongoDB 8.2.x versions: Upgrade to version 8.2.2
  7. 7. After upgrading, verify that the certificate validation now correctly enforces Extended Key Usage (EKU) requirements: clientAuth for client certificates and serverAuth for server certificates
  8. 8. Restart the MongoDB service and confirm normal operation
Caveat Standard MongoDB upgrade considerations apply: ensure backups before upgrading, review release notes for any between-version changes, and test in non-production environments first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MongoDB Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12893 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data