CVE-2026-119179: MongoDB Node.js driver: Connection pool desynchronization after operation timeout can expose other user's data
MongoDB · Node.js Driver
Vendor fix available · Affected: MongoDB Node.js Driver · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 23% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- MongoDB · Node.js Driverfrom 6.11.0 before 6.22.0; from 7.0.0 before 7.8.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- MongoDB
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-119179 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.