Secuno
ENNL
Book demo

CVE-2025-3085

Mongodb vulnerability

8.1 HIGHEPSS 0.27%
  1. Published1 Apr 2025

Description

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

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Mongodb≥ 5.0.0 < 5.0.31 · ≥ 6.0.0 < 6.0.20 · ≥ 7.0.0 < 7.0.16 · ≥ 8.0.0 < 8.0.4

Remediation

Fixed in
Mongodb≥ 5.0.31

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-616998.1
nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version…

Frequently asked

Is CVE-2025-3085 being actively exploited?

CVE-2025-3085 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.27%.

How severe is CVE-2025-3085?

CVE-2025-3085 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.27% probability of exploitation.

Which products are affected by CVE-2025-3085?

Affected products include Mongodb.

How do I fix CVE-2025-3085?

Upgrade affected software to a fixed version, for example Mongodb 5.0.31 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-3085 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.