CyberSecBulletin
CVE-2026-119179NVD status: Awaiting Analysis

Node.js Driver: Sensitive Information in Resource Not Removed Before Reuse

Published Updated By the CyberSecBulletin desk

CVE-2026-119179 is a high-severity sensitive information in resource not removed before reuse vulnerability in Node.js Driver from MongoDB, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 6.22.0, 7.8.0 as the first without the flaw, so updating Node.js Driver to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.3% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Node.js Driver to 6.22.0 or 7.8.0, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
MongoDBNode.js Driver6.11.0 up to, but not including, 6.22.0; 7.0.0 up to, but not including, 7.8.06.22.0, 7.8.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
LowLimited modification of data is possible.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L. Scored by CNA (mongodb.com).

Scoring systemScoreSeverityScored by
CVSS 4.08.3HighCNA (mongodb.com)
CVSS 3.17.0HighCNA (mongodb.com)

Official description

A flaw in the connection management layer of the MongoDB Node.js driver can leave a pooled network connection in the pool for reuse while data from an earlier operation is still outstanding on it. In applications that enable an optional client-side operation timeout, an unauthenticated party that can send ordinary requests to the application may cause database replies to be paired with the wrong requests. This may result in unintended disclosure of other users' records, incorrect operation results being returned, and failures of legitimate requests.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Sensitive Information in Resource Not Removed Before Reuse

The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or zeroize the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.

How developers prevent this class of flaw

  • During critical state transitions, information not needed in the next state should be removed or overwritten with fixed patterns (such as all 0's) or random data, before the transition to the next state.
  • Be careful using vfork() and fork() in security sensitive code. The process state will not be cleaned up and will contain traces of data from past use.

More Sensitive Information in Resource Not Removed Before Reuse vulnerabilities (CWE-226)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).

References

Other vulnerabilities in Node.js Driver

All Node.js Driver vulnerabilities

Recent Sensitive Information in Resource Not Removed Before Reuse vulnerabilities

Spotted an error? Tell us.