Skip to main content
VulnerabilityPublished

CVE-2026-120819: MongoDB Server · Use After Free

Affects MongoDB ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 9.0.7 when convenient.

Data as of 10 Nov 2026, 20:36 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (mongodb)CVSS 4.05.3
CNA (mongodb)CVSS 3.14.3
Patch
Available – fixed in 9.0.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

Affected software

ProductAffectedFixed in
MongoDBMongoDB ServerAffected
  • >=9.0.0 <9.0.7
Fixed in
  • 9.0.7

AI-suggested

Upgrade MongoDB Server to version 9.0.7 or later, where this use-after-free vulnerability is fixed. No other mitigation is required as the issue is resolved in the official patch.

Description

CVE-2026-120819 is a use-after-free vulnerability in the server-side JavaScript execution component of MongoDB Server. An authenticated user with read-only privileges can exploit this flaw by submitting a specially crafted database command that executes user-supplied JavaScript. This causes the server to access memory that has already been freed, potentially leaking adjacent process memory in the command's result. The vulnerability allows unauthorized information disclosure but does not affect data integrity or service availability. The issue is fixed in MongoDB Server version 9.0.7.

References

Community reviews

Loading reviews…