Is CVE-2026-120828 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-120828 being exploited in the wild.

How severe is CVE-2026-120828?

High severity, with a CVSS score of 7.5, published 10 November 2026.

Which products and versions are affected?

MongoDB 4.4 before 4.4.32, 5.0 before 5.0.35, 6.0 before 6.0.30, 7.0 before 7.0.48, 8.0 before 8.0.37, 8.3 before 8.3.16, 9.0 before 9.0.7.

Is there a fix for CVE-2026-120828?

Yes: fixed in MongoDB 4.4.32, 5.0.35, 6.0.30, 7.0.48, 8.0.37, 8.3.16, 9.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-120828 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-120828?

Check whether you run MongoDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-120828: MongoDB replica-set denial of service via unreclaimed wait records

CVE-2026-120828 · Severity: high · CVSS 7.5 · Published 2026-11-10

MongoDB is a database server commonly used in production environments to store application data. An attacker with network access but no credentials can send specially crafted requests with a read option pointing to an unreachable point in time, causing the server to accumulate internal memory records without bound. This leads to memory exhaustion, causing the database to become unavailable and disrupting dependent applications.

Technologies: MongoDB. Vendors: MongoDB.

Quick answers

Is CVE-2026-120828 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-120828 being exploited in the wild.
How severe is CVE-2026-120828?: High severity, with a CVSS score of 7.5, published 10 November 2026.
Which products and versions are affected?: MongoDB 4.4 before 4.4.32, 5.0 before 5.0.35, 6.0 before 6.0.30, 7.0 before 7.0.48, 8.0 before 8.0.37, 8.3 before 8.3.16, 9.0 before 9.0.7.
Is there a fix for CVE-2026-120828?: Yes: fixed in MongoDB 4.4.32, 5.0.35, 6.0.30, 7.0.48, 8.0.37, 8.3.16, 9.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-120828 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-120828?: Check whether you run MongoDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: MongoDB 4.4.32, 5.0.35, 6.0.30, 7.0.48, 8.0.37, 8.3.16, 9.0.7

Technical details

A replica-set database server node fails to limit or reclaim internal wait records created when processing a client-supplied readConcern option with an afterOpTime value the node will never reach. An unauthenticated attacker with network access can exploit this by sending requests that accumulate unbounded memory records persisting after the request completes, triggering an out-of-memory condition and server unavailability.

Affected products

MongoDB MongoDB 4.4 before 4.4.32, 5.0 before 5.0.35, 6.0 before 6.0.30, 7.0 before 7.0.48, 8.0 before 8.0.37, 8.3 before 8.3.16, 9.0 before 9.0.7

Timeline

2026-11-10: disclosed

References

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.