Quick answers
- Is CVE-2026-120820 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120820 being exploited in the wild.
- How severe is CVE-2026-120820?
- Medium severity, with a CVSS score of 4.3, published 10 November 2026.
- Which products and versions are affected?
- MongoDB Server before 8.0.37, 8.3.16, 9.0.7.
- Is there a fix for CVE-2026-120820?
- Yes: fixed in 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-120820 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120820?
- 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: 8.0.37, 8.3.16, 9.0.7
Technical details
The vulnerability exists in fle_stats.cpp where the registerCollectionStats() function creates map entries for any namespace in a request without limiting the number of entries or providing removal mechanisms. The entries are created before transaction validation, so entries persist even if operations fail. On mongos nodes, entries are never removed because there is no local collection catalog. An authenticated user with find, insert, update, or delete privileges can exploit this by sending QE-shaped commands against non-existent or unencrypted collections with arbitrary namespace names, each creating a permanent memory allocation.
Affected products
- MongoDB Server before 8.0.37, 8.3.16, 9.0.7
Timeline
- 2026-11-10: disclosed
- 2026-11-10: patched