CVSS 4.0
8.3 highCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:NCVE-2026-119179
High (8.3) in mongodb node.js driver. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
CVSS 3.1
7.0 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-226 Sensitive Information in Resource Not Removed Before Reuse
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-119179 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119179?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119179?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-119179 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- mongodb:node.js driver
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| MongoDB Node.js Driver | from 6.11.0 before 6.22.0 |
| MongoDB Node.js Driver | from 7.0.0 before 7.8.0 |
Red Hat
Red Hat rates this Moderate.
This vulnerability is evaluated as having a Moderate impact for Red Hat products because successful exploitation requires specific asynchronous race conditions and relies on optional client-side operation timeout settings. Within Red Hat environments, such as containerized services in OpenShift Data Foundation and OpenShift Serverless, the driver is utilized internally, limiting direct exposure to arbitrary caller manipulation. Furthermore, attackers cannot reliably target specific database records, as the misassociation of incoming responses depends on random traffic volume and socket recycling timing.
--- CME Mitigation Guidance (2026-11-04) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to disable client-side operation timeouts (timeoutMS) in MongoDB Node.js driver connection configurations: upgrade to mongodb 6.22.0 or 7.8.0 (or the fixed Odf4/Mcg Core Rhel/Openshift Serverless 1/Logic Rhel9 Operator builds), which ignore the timeoutMS option as a no-op during option parsing, closing all 2 injection vectors (request-response desynchronization via timed-out connection reuse, concurrent application requests triggering client-side operation timeouts). Until patched, this is a concern on Applications running MongoDB Node.js driver versions 6.11.0-6.21.x or 7.0.0-7.7.x that enable client-side operation timeouts (timeoutMS), so Remove or avoid configuring the timeoutMS client-side operation timeout option across all application database client instances. These controls limit blast radius and contain exploitation, but they do not fix the underlying connection pool desynchronization defect — apply the upstream patch to fully remediate.
| Product | Package | State | Advisory |
|---|---|---|---|
| OpenShift Serverless | openshift-serverless-1/logic-rhel9-operator | Affected | |
| Red Hat Openshift Data Foundation 4 | odf4/mcg-core-rhel9 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-119179.
Attack patterns (CAPEC)
- CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.