MongoDBDatabase / datastore
CVE-2025-6713
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 · uneditedAn unauthorized user may leverage a specially crafted aggregation pipeline to access data without proper authorization due to improper handling of the $mergeCursors stage in MongoDB Server. This may lead to access to data without further authorisation. This issue affects MongoDB Server MongoDB Server v8.0 versions prior to 8.0.7, MongoDB Server v7.0 versions prior to 7.0.19 and MongoDB Server v6.0 versions prior to 6.0.22
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 has an authorization bypass vulnerability in the aggregation framework where the $mergeCursors stage, when supplied with a specially crafted aggregation pipeline, can allow unauthorized users to access data without proper authorization checks.
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.22>= 7.0.0, < 7.0.19>= 8.0.0, < 8.0.7CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed MongoDB Server versionRun db.version() in the mongo shell or use mongod --version from the command lineAffected if The version falls within the affected ranges: 6.0.0 to 6.0.21, 7.0.0 to 7.0.18, or 8.0.0 to 8.0.6
-
Determine if aggregation pipelines are in useReview application code and database queries for any aggregation operations. Check the output of db.getCollection('collection_name').aggregate() calls in logs or application tracesAffected if The environment uses aggregation pipelines, particularly those that may involve multiple cursors or sharded cluster operations
-
Check for $mergeCursors stage usage in aggregation pipelinesSearch MongoDB logs and profiler output for 'mergeCursors' or examine any aggregation pipeline definitions that involve merging results from multiple shards or collectionsAffected if Aggregation pipelines containing $mergeCursors or similar merge operations are being executed against the database
-
Review user authorization for aggregation operationsRun db.getUsers() or db.getRoles() to list users and their roles. Check if users with limited roles are performing aggregation operations that may access data outside their authorized collectionsAffected if Users with restricted roles have access to aggregation operations that could potentially bypass authorization checks on the $mergeCursors stage
The environment is affected if MongoDB Server version is 6.0.0-6.0.21, 7.0.0-7.0.18, or 8.0.0-8.0.6 AND aggregation pipelines using $mergeCursors are in use with users who may have limited authorization.
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.227.0.198.0.7
Upgrade MongoDB Server to v8.0.7, v7.0.19, or v6.0.22 or later to address the improper handling of the $mergeCursors stage in the aggregation pipeline.
6.0.22 (for 6.0.x), 7.0.19 (for 7.0.x), or 8.0.7 (for 8.0.x)
- 1. Identify the current MongoDB Server version using: db.version() or mongod --version
- 2. Determine which upgrade path applies based on current version: 6.0.x → 6.0.22, 7.0.x → 7.0.19, or 8.0.x → 8.0.7
- 3. Review MongoDB upgrade documentation for your current major version for prerequisites and migration steps
- 4. Create a full backup of all databases before upgrading
- 5. Test the upgrade in a non-production environment first
- 6. Schedule a maintenance window with appropriate downtime
- 7. Upgrade MongoDB Server to the appropriate fixed version (6.0.22, 7.0.19, or 8.0.7) using your package manager or binary installation method
- 8. Verify the upgrade was successful and the server starts without errors
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6713 — 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-6713 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