MongoDBDatabase / datastore
CVE-2025-6709
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 · uneditedThe MongoDB Server is susceptible to a denial of service vulnerability due to improper handling of specific date values in JSON input when using OIDC authentication. This can be reproduced using the mongo shell to send a malicious JSON payload leading to an invariant failure and server crash. This issue affects MongoDB Server v7.0 versions prior to 7.0.17 and MongoDB Server v8.0 versions prior to 8.0.5. The same issue affects MongoDB Server v6.0 versions prior to 6.0.21, but an attacker can only induce denial of service after authenticating.
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 confidenceMongoDB Server contains a denial of service vulnerability in its JSON parsing of date values when OIDC authentication is enabled. An attacker can send a specially crafted JSON payload via the mongo shell containing malicious date values, triggering an invariant failure that causes the server to crash. The vulnerability affects versions prior to 7.0.17 and 8.0.5 (unauthenticated attack vector), and v6.0 prior to 6.0.21 (requires authentication).
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
>= 6.0.0, < 6.0.21>= 7.0.0, < 7.0.17>= 8.0.0, < 8.0.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check MongoDB server versionRun `db.version()` in the mongo shell or execute `mongod --version` from the command line to obtain the installed MongoDB versionAffected if The version is 6.0.x before 6.0.21, 7.0.x before 7.0.17, or 8.0.x before 8.0.5
-
Identify OIDC authentication configurationInspect the MongoDB configuration file (typically /etc/mongod.conf or the file specified via --config). Look for the `security.authorization` setting and OIDC-related configuration blocks under `security`Affected if OIDC authentication is explicitly enabled in the configuration file under the security section
-
Confirm OIDC provider settingsCheck for OIDC-specific configuration parameters such as `issuer`, `audience`, or OIDC provider URIs in the mongod.conf file or by querying the server status with `db.adminCommand({getParameter: 1, oidcAuth: 1})` if permissions allowAffected if OIDC authentication parameters are present and configured on the server
-
Verify if mongo shell access is exposedCheck network exposure of the mongo shell interface by reviewing bindIp settings in the configuration and firewall rules. Ensure port 27017 (default) is not accessible from untrusted networksAffected if The MongoDB server is reachable from network segments where untrusted users could send malicious JSON payloads via the mongo shell
The environment is affected if running a vulnerable MongoDB version (6.0.x < 6.0.21, 7.0.x < 7.0.17, or 8.0.x < 8.0.5) AND OIDC authentication is enabled, allowing specially crafted JSON date values to trigger a denial of service.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.0.217.0.178.0.5
Upgrade MongoDB Server to version 7.0.17+, 8.0.5+, or 6.0.21+ to patch the vulnerability. For v6.0 deployments, ensure OIDC authentication is properly configured and consider upgrading given the authenticated attack vector.
Upgrade to MongoDB Server 6.0.21 (if on 6.0.x), 7.0.17 (if on 7.0.x), or 8.0.5 (if on 8.0.x)
- 1. Schedule a maintenance window for the MongoDB upgrade
- 2. Back up all MongoDB databases and configuration files
- 3. Download the appropriate MongoDB Server version for your current release branch: 6.0.21, 7.0.17, or 8.0.5
- 4. For standalone instances: stop the MongoDB service, replace the binaries, and restart
- 5. For replica sets: perform a rolling upgrade following MongoDB's rolling upgrade procedure (upgrade secondary members first, then primary)
- 6. Verify the MongoDB service starts successfully and accepts connections
- 7. Test application functionality to confirm the upgrade does not break existing operations
- 8. For OIDC authentication configurations, verify the authentication mechanism functions correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6709 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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