MongoDB Node.js driver: Connection pool desynchronization after operation timeout can expose other user's data
Affects MongoDB Node.js Driver 6.11.0 to before 6.22.0 and 7.0.0 to before 7.8.0. The fix is listed as 7.8.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.22.0, 7.8.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.22.0, 7.8.0.
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
CVE-2026-119179 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects Node.js Driver; fixed in 6.22.0 and 7.8.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 6.22.0, 7.8.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The MongoDB Node.js driver is affected when applications enable the optional client-side operation timeout. The flaw can cause database responses to be matched with the wrong requests, which may expose other users' records, return incorrect results, or cause legitimate requests to fail.
Read the original 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.
What to do
Upgrade to a fixed version: 6.22.0, 7.8.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- MongoDB Node.js Driver
From 6.11.0 · fixed in 6.22.0; From 7.0.0 · fixed in 7.8.0
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119179
Is CVE-2026-119179 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-119179?
Node.js Driver: from 6.11.0 before 6.22.0; from 7.0.0 before 7.8.0.Source: cve.now feed data
How do I fix CVE-2026-119179?
Upgrade to 7.8.0 or later on the 7.x line, or to 6.22.0 or later on the 6.x line. The 6.x line is fixed starting at 6.22.0 per the affected ranges.Source: jira.mongodb.org