MongoDBDatabase / datastore
CVE-2025-3082
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 · uneditedA user authorized to access a view may be able to alter the intended collation, allowing them to access to a different or unintended view of underlying data. This issue affects MongoDB Server v5.0 version prior to 5.0.31, MongoDB Server v6.0 version prior to 6.0.20, MongoDB Server v7.0 version prior to 7.0.14 and MongoDB Server v7.3 versions prior to 7.3.4.
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 · moderate confidenceA MongoDB Server vulnerability allows users authorized to access a view to manipulate the collation parameter, enabling them to bypass intended view restrictions and access a different or unintended view of the underlying data. This is an authorization bypass through collation manipulation.
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
>= 5.0.0, < 5.0.31>= 6.0.0, < 6.0.20>= 7.0.0, < 7.0.14>= 7.3.0, < 7.3.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check MongoDB Server versionRun db.version() in mongosh or use mongod --version to retrieve the installed server versionAffected if The version falls within any of these ranges: >= 5.0.0 and < 5.0.31, >= 6.0.0 and < 6.0.20, >= 7.0.0 and < 7.0.14, or >= 7.3.0 and < 7.3.4
-
Identify views in databasesRun db.getCollectionInfos({type: 'view'}) against each database to list all defined viewsAffected if Any views exist in the database (the vulnerability allows bypassing view restrictions on existing views)
-
Inspect view definitions for custom collationsRun db.getCollectionInfos({type: 'view'}) and examine the collation field in each view definition to see if custom collations are definedAffected if Views with custom collation settings are present, as the vulnerability exploits collation parameter manipulation
-
Review user permissions on viewsRun db.getUser() or db.getRole() for users with read or readWrite access to view collections, and check db.getCollection('viewname').getIndexes() to see collation configurationsAffected if Users have permissions on views that utilize custom collations
You are affected if your MongoDB version is within the vulnerable ranges AND you have views defined with custom collation settings accessible to users.
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 · scoped5.0.316.0.207.0.14
Upgrade MongoDB Server to version 5.0.31 or higher (v5.0), 6.0.20 or higher (v6.0), 7.0.14 or higher (v7.0), or 7.3.4 or higher (v7.3). Review existing view definitions and user permissions as part of the upgrade process.
Upgrade to the minimum fixed version for your branch: 5.0.31, 6.0.20, 7.0.14, or 7.3.4
- 1. Identify the currently installed MongoDB Server version using: db.version() in the mongo shell or 'mongod --version'
- 2. Determine which version branch you are running (5.0.x, 6.0.x, 7.0.x, or 7.3.x)
- 3. For MongoDB 5.0.x: Upgrade to version 5.0.31 or later
- 4. For MongoDB 6.0.x: Upgrade to version 6.0.20 or later
- 5. For MongoDB 7.0.x: Upgrade to version 7.0.14 or later
- 6. For MongoDB 7.3.x: Upgrade to version 7.3.4 or later
- 7. Before upgrading, review the MongoDB release notes for your target version for any required migration steps
- 8. Ensure you have a complete backup of your data before performing the 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
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3082 — 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-3082 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