Quick answers
- Is CVE-2026-120810 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120810 being exploited in the wild.
- How severe is CVE-2026-120810?
- Medium severity, with a CVSS score of 6.5, published 10 November 2026.
- Which products and versions are affected?
- MongoDB Server 7.0.x, 8.0.x, 8.2.x, 8.3.x, 9.0.x (before fixed versions).
- Is there a fix for CVE-2026-120810?
- Yes: fixed in 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-120810 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120810?
- Check whether you run MongoDB Server 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: 7.0.48, 8.0.37, 8.3.16, 9.0.7
Technical details
The $_internalKeyStringValue expression in MongoDB's aggregation framework lacks input validation and memory limits, allowing authenticated users to trigger unbounded memory allocations. An attacker with read privileges can send crafted aggregate commands across multiple concurrent connections, exhausting server memory until the mongod process is terminated by the OS out-of-memory killer. A fix implementing the internalQueryKeyStringValueMaxCollationBytes parameter to enforce memory limits has been released.
Affected products
- MongoDB MongoDB Server 7.0.x, 8.0.x, 8.2.x, 8.3.x, 9.0.x (before fixed versions)
Timeline
- 2026-11-10: disclosed
- 2026-11-10: patched