Skip to main content
VulnerabilityPublished

CVE-2026-4147: MongoDB Server · Use of Uninitialized Variable

Affects MongoDB ServerSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.2.6, 8.0.20, 7.0.31
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Mar 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 30 Oct 2026.

What to do

Upgrade MongoDB Server to 8.2.6, 8.0.20 or 7.0.31.

Affected software

ProductAffectedFixed in
MongoDB IncMongoDB ServerAffected
  • >=8.2 <8.2.6
Fixed in
  • 8.2.6
MongoDB IncMongoDB ServerAffected
  • >=8.0 <8.0.20
Fixed in
  • 8.0.20
MongoDB IncMongoDB ServerAffected
  • >=7.0 <7.0.31
Fixed in
  • 7.0.31

AI-suggested

  1. Monitor MongoDB usage logs for unusual or excessive filemd5 command invocations, especially from users with read roles.
  2. Restrict read role assignments strictly to trusted and necessary users; implement the principle of least privilege.
  3. 4. Consider implementing network segmentation and access controls to limit exposure of MongoDB instances to only authorized systems and users. 5. Use encryption at rest and in transit to reduce the impact of any leaked data. 6. Conduct regular audits of user permissions and review authentication mechanisms to detect and prevent unauthorized access. 7. Employ runtime application self-protection (RASP) or database activity monitoring tools that can detect anomalous command usage patterns. 8. If patching is delayed, consider disabling or restricting the filemd5 command usage via MongoDB configuration or role-based access control where feasible.

Description

An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command.

References

Community reviews

Loading reviews…