MongoDB Node.js Driver
MongoDB Node.js driver: Connection pool desynchronization after operation timeout can expose other user's data
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 6.11.0, < 6.22.0
- >= 7.0.0, < 7.8.0
Fixed in 6.22.0, 7.8.0
Mitigation
Upgrade Node.js Driver to 6.22.0 or 7.8.0 or later.
Timeline
Days relative to CVE publicationFirst public PoC 13 days after publication; not in CISA KEV. First PoC: LLCForge/CVE-2026-119179 (created 16 Nov 2026, found by us: 16 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| LLCForge/CVE-2026-119179 | 16 Nov 2026 +13 d | 16 Nov 2026 | 0 | PoC
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.