Skip to main content
VulnerabilityPublished

CVE-2026-120806: MongoDB Server · Incomplete Cleanup

Affects MongoDB ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High · fixed in 9.0.7 : patch MongoDB Server soon.

Data as of 10 Nov 2026, 20:47 UTC

CVSS 4.0 base score
7.0High
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.07.0
CNA (mongodb)CVSS 3.15.5
Patch
Available – fixed in 9.0.7, 8.3.16, 8.0.37 +1
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/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, 8.3.16, 8.0.37 or 7.0.48.

Affected software

ProductAffectedFixed in
MongoDBMongoDB ServerAffected
  • >=9.0.0 <9.0.7
Fixed in
  • 9.0.7
MongoDBMongoDB ServerAffected
  • >=8.3.0 <8.3.16
Fixed in
  • 8.3.16
MongoDBMongoDB ServerAffected
  • >=8.0.0 <8.0.37
Fixed in
  • 8.0.37
MongoDBMongoDB ServerAffected
  • >=7.0.0 <7.0.48
Fixed in
  • 7.0.48

AI-suggested

A fix is available in MongoDB Server versions 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. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-120806 is a vulnerability in MongoDB Server affecting versions 7.0.0 through 7.0.47, 8.0.0 through 8.0.36, 8.3.0 through 8.3.15, and 9.0.0 through 9.0.6. It involves incomplete cleanup of role authorization data when roles are dropped, causing stale references to persist in user and role documents. This can lead to users silently inheriting privileges from newly created roles with the same name without explicit grants or audit events. Exploitation requires authenticated administrative access to the database. The issue is fixed in versions 7.0.48, 8.0.37, 8.3.16, and 9.0.7.

References

Community reviews

Loading reviews…