MongoDBDatabase / datastore
CVE-2025-13643
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 with access to the cluster with a limited set of privilege actions may be able to terminate queries that are being executed by other users. This may cause a denial of service by preventing a fraction of queries from successfully completing. This issue affects MongoDB Server v7.0 versions prior to 7.0.26 and MongoDB Server v8.0 versions prior to 8.0.14
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 a broken access control vulnerability where users with limited privileges can terminate queries executing as other users, causing denial of service. This affects v7.0 prior to 7.0.26 and v8.0 prior to 8.0.14.
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
>= 7.0.0, < 7.0.26>= 8.0.0, < 8.0.14= 8.2.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed MongoDB Server versionRun 'db.version()' in the mongo shell or use 'mongod --version' from command lineAffected if Version is >= 7.0.0 and < 7.0.26, OR >= 8.0.0 and < 8.0.14, OR equals 8.2.0
-
Identify users with database accessRun 'use admin' followed by 'db.system.users.find()' to list all users in the systemAffected if More than one user exists with any read, readWrite, or custom application role
-
Verify role assignments for non-admin usersRun 'db.getRoles({rolesInfo: 1, showPrivileges: true})' to review all defined roles and their privilegesAffected if Any role grants 'killop' or 'killAnyCursor' privileges to users who should not have administrative access
-
Test query termination by low-privilege userAs a non-admin user, run 'db.adminCommand({currentOp: 1})' to find other users' operations, then attempt 'db.killOp(<opId>)' on an operation owned by a different userAffected if The low-privilege user successfully terminates another user's query (demonstrates the vulnerability)
You are affected if your MongoDB version falls within the vulnerable ranges AND multiple users exist with database access, allowing a limited-privileged user to terminate another user's queries.
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 · scoped7.0.268.0.14
Upgrade MongoDB Server to v7.0.26 or v8.0.14 or later. Apply least-privilege principles to user roles until the upgrade is completed.
MongoDB Server 7.0.26+ (for 7.0.x) or 8.0.14+ (for 8.0.x) or next patch after 8.2.0
- 1. Identify the currently installed MongoDB Server version using: db.version() or mongod --version
- 2. For MongoDB Server 7.0.x: Upgrade to version 7.0.26 or later
- 3. For MongoDB Server 8.0.x (excluding 8.2.0): Upgrade to version 8.0.14 or later
- 4. For MongoDB Server 8.2.0: Upgrade to the next available patch release (e.g., 8.2.1 or later) that includes the security fix
- 5. Before upgrading in production, backup all data and configuration files
- 6. Test the upgrade in a staging environment to verify application compatibility
- 7. During upgrade, ensure rolling upgrade procedures are followed to maintain cluster availability
- 8. After upgrade, verify that the fix is applied by confirming the MongoDB version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13643 — 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-13643 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