Skip to main content
VulnerabilityPublished

CVE-2026-118383: Use After Free

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-118383· Critical 9.5

Not known to be exploited · CVSS 9.5 Critical · fixed in 9.0.7 : patch MongoDB Server as a priority.

Data as of 10 Nov 2026, 22:37 UTC

CVSS 4.0 base score
9.5Critical
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.09.5
CNA (mongodb)CVSS 3.19.0
Patch
Available – fixed in 9.0.7, 8.3.16, 8.0.37 +4
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

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 to a fixed release listed under Affected software.

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
MongoDBMongoDB ServerAffected
  • >=6.0.0 <6.0.30
Fixed in
  • 6.0.30
MongoDBMongoDB ServerAffected
  • >=5.0.0 <5.0.35
Fixed in
  • 5.0.35

AI-suggested

If you cannot patch yet, restrict access to MongoDB replica set members to trusted networks and monitor for unusual behavior. Note that standalone mongod instances are not affected.

Description

CVE-2026-118383 is a critical use-after-free vulnerability in the replication component of MongoDB Server. It occurs when a newly elected replica set primary completes catch-up. The flaw can be triggered by unauthenticated requests and may cause the server to crash or, under certain conditions, allow arbitrary code execution. This affects replica set members, including shard and config server replica sets in sharded clusters, but not standalone mongod instances.

References

Community reviews

Loading reviews…