dbcve.org
MongoDBDatabase / datastore

CVE-2025-3085

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 5.0.31 / 6.0.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A MongoDB server under specific conditions running on Linux with TLS and CRL revocation status checking enabled, fails to check the revocation status of the intermediate certificates in the peer's certificate chain. In cases of MONGODB-X509, which is not enabled by default, this may lead to improper authentication. This issue may also affect intra-cluster authentication. This issue affects MongoDB Server v5.0 versions prior to 5.0.31, MongoDB Server v6.0 versions prior to 6.0.20, MongoDB Server v7.0 versions prior to 7.0.16 and MongoDB Server v8.0 versions prior to 8.0.4. Required Configuration : MongoDB Server must be running on Linux Operating Systems and CRL revocation status checking must be enabled

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 on Linux with TLS and CRL revocation checking enabled fails to verify the revocation status of intermediate certificates in the peer certificate chain, only checking the leaf certificate. This allows potentially compromised intermediate CAs to authenticate when using MONGODB-X509 authentication or intra-cluster authentication.

MitigationUpgrade MongoDB Server to v5.0.31+, v6.0.20+, v7.0.16+, or v8.0.4+ as appropriate, or disable CRL checking if not required for the deployment.

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:>= 5.0.0, < 5.0.31>= 6.0.0, < 6.0.20>= 7.0.0, < 7.0.16>= 8.0.0, < 8.0.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 MongoDB Server version
    Run 'mongod --version' or 'db.version()' from a mongo shell to get the installed version number.
    Affected if The version falls within < 5.0.31, < 6.0.20, < 7.0.16, or < 8.0.4 for their respective branches.
  2. Verify TLS is enabled
    Check the MongoDB configuration file (typically /etc/mongod.conf) or run 'db.adminCommand({getParameter: 1, tlsMode: 1})' to see if TLS is configured.
    Affected if TLS is enabled (tlsMode is not disabled or unknown).
  3. Confirm CRL checking is enabled
    Inspect the MongoDB configuration for 'net.tls.CRLFile' or 'net.tls.crlFile' setting, or check runtime with 'db.adminCommand({getParameter: 1, tlsCRLFile: 1})'. This setting enables Certificate Revocation List checking.
    Affected if A CRLFile path is specified and CRL checking is active.
  4. Check for X.509 or cluster authentication in use
    Review the authentication configuration in mongod.conf under 'security.authenticationMechanisms' or 'security.clusterAuthMode', or query with 'db.adminCommand({getCmdLineOpts: 1})'.
    Affected if MONGODB-X509 authentication or intra-cluster authentication (keyFile/internal authentication) is configured.

All four conditions must be true for the system to be affected: vulnerable MongoDB version, TLS enabled, CRL checking enabled, and X.509 or cluster authentication in use.

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 5.0.31 / 6.0.20 / 7.0.16 or later
Fixed in 5.0.316.0.207.0.16
Interim mitigation

Upgrade MongoDB Server to v5.0.31+, v6.0.20+, v7.0.16+, or v8.0.4+ as appropriate, or disable CRL checking if not required for the deployment.

Recommended fix High confidence

5.0.31 (for 5.0.x) | 6.0.20 (for 6.0.x) | 7.0.16 (for 7.0.x) | 8.0.4 (for 8.0.x)

  1. Identify current MongoDB version using: db.version() or mongod --version
  2. Determine the appropriate fixed version based on your current major version branch: 5.0.x → 5.0.31, 6.0.x → 6.0.20, 7.0.x → 7.0.16, or 8.0.x → 8.0.4
  3. Review MongoDB upgrade documentation for your specific version migration path
  4. Create a full backup of all databases before proceeding with upgrade
  5. Stop the MongoDB service: sudo systemctl stop mongod
  6. Upgrade MongoDB using your package manager (apt/yum/dnf) to the appropriate fixed version
  7. Start the MongoDB service: sudo systemctl start mongod
  8. Verify the version has been updated: db.version()
Caveat Minor version upgrades within the same major version are typically low-risk; consult release notes for any specific compatibility notes

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3085 — 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-3085 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