MongoDBDatabase / datastore
CVE-2026-8200
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 · uneditedWhen schema validation is enabled on a collection and an update or insert would violate the collection's schema, the local server log message generated may not have all user data redacted. This issue impacts MongoDB Server v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.
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 confidenceThis MongoDB vulnerability allows unredacted user data to potentially appear in server logs when schema validation is enabled and an insert/update violates the collection's schema. The issue stems from incomplete data sanitization in error/logging paths, potentially exposing sensitive user information in plaintext logs.
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.34>= 8.0.0, < 8.0.23>= 8.2.0, < 8.2.9>= 8.3.0, < 8.3.2CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check installed MongoDB Server versionRun `db.version()` in mongosh/mongo shell or execute `mongod --version` / `mongos --version` to obtain the exact version stringAffected if The version falls within >= 7.0.0 and < 7.0.34, OR >= 8.0.0 and < 8.0.23, OR >= 8.2.0 and < 8.2.9, OR >= 8.3.0 and < 8.3.2
-
Identify collections with schema validation enabledQuery collections with validators using `db.getCollectionInfos({$where: 'this.validator !== null'})` or iterate through each database and check for collections with `collMod` or `create` validationOptions configuredAffected if Any collection in the database has JSON schema validation or constraint-based validation configured via the validator option
-
Review MongoDB server logs for schema validation error messagesExamine MongoDB log files (default path /var/log/mongodb/ or custom logPath) for entries containing 'Schema validation failed' or validation error messages related to insert/update operationsAffected if Log files contain schema validation failure messages that may include plaintext user data from the document being inserted or updated
You are affected if your MongoDB version is within the affected ranges AND you have collections with schema validation enabled, as the vulnerability requires both conditions to expose unredacted user data in logs.
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.348.0.238.2.9
Upgrade MongoDB Server to version 7.0.34+, 8.0.23+, 8.2.9+, or 8.3.2+ to patch the incomplete user data redaction in schema validation log messages.
Upgrade to MongoDB Server 7.0.34, 8.0.23, 8.2.9, or 8.3.2 (or later) depending on your major version branch
- 1. Check current MongoDB server version by running: db.version() in the mongo shell or 'mongod --version' from command line
- 2. Determine which version branch you are currently running (7.0.x, 8.0.x, 8.2.x, or 8.3.x)
- 3. Perform a full backup of all databases before upgrading
- 4. Test the upgrade in a non-production environment first
- 5. For production upgrade, follow MongoDB's standard upgrade procedure: ensure replica set members are upgraded one at a time, or for standalone instances stop the server, replace the binary, and restart
- 6. After upgrade, verify the new version is running with: db.version()
- 7. Enable schema validation on test collections and verify that log output properly redacts user data
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
- 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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8200 — 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-2026-8200 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