CVE-2026-120811: MongoDB Server · Use After Free
Affects MongoDB ServerSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium · fixed in 9.0.7 : update MongoDB Server when convenient.
Data as of 10 Nov 2026, 20:34 UTC
Thin evidence
One scorer or none| CNA (mongodb) | CVSS 4.0 | 6.0 |
|---|---|---|
| CNA (mongodb) | CVSS 3.1 | 5.9 |
- Patch
- Available – fixed in 9.0.7, 8.3.16, 8.0.37 +1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade MongoDB Server to 9.0.7, 8.3.16, 8.0.37 or 7.0.48.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDBMongoDB Server | Affected
| Fixed in
|
| MongoDBMongoDB Server | Affected
| Fixed in
|
| MongoDBMongoDB Server | Affected
| Fixed in
|
| MongoDBMongoDB Server | Affected
| Fixed in
|
AI-suggested
Fixed versions are available: 7.0.48, 8.0.37, 8.3.16, and 9.0.7. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication that the vulnerability is mitigated by default or that no action is required. No additional temporary mitigations are described.
Description
CVE-2026-120811 is a use-after-free vulnerability in the MongoDB Server's classic query engine plan cache. It occurs when cached plan statistics retain unowned references to data from earlier commands after the memory has been freed. This can lead to reading freed heap memory during diagnostic commands, potentially exposing sensitive server memory contents to authenticated clients. Under certain conditions, it may also cause the server to crash. The issue affects multiple MongoDB Server versions and has been assigned a medium severity rating.