Quick answers
- Is CVE-2026-119179 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119179 being exploited in the wild.
- How severe is CVE-2026-119179?
- High severity, with a CVSS score of 7, published 3 November 2026.
- Which products and versions are affected?
- MongoDB Node.js Driver before 7.8.0.
- Is there a fix for CVE-2026-119179?
- Yes: fixed in 7.8.0 (also backported to 6.22.0). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119179 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119179?
- Check whether you run MongoDB Node.js Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.8.0 (also backported to 6.22.0)
Technical details
The vulnerability exists in the connection management layer where pooled network connections can be reused while outstanding data from a previous operation remains on them. When client-side operation timeout (timeoutMS) is enabled, an unauthenticated attacker can send requests that cause database replies to be paired with incorrect requests. The fix in version 7.8.0 makes timeoutMS a no-op, removing the dangerous timeout feature entirely in favor of safer alternatives.
Affected products
- MongoDB Node.js driver before 7.8.0
Timeline
- 2026-11-03: disclosed
- 2026-10-30: patched