Skip to content
major vulnerability· requires attention

Affects the widely used MongoDB Node.js driver; can leak user data across requests in Node.js backends—broad impact across organizations using Node/MongoDB.

Applications

CVE-2026-119179

8.3
High
EPSS n/a

Connection-pool bug in MongoDB Node.js driver can misroute DB responses

exploited
No known exploitation not in CISA KEV as of our last sync
fix
No fixed release stated by the publisher
likelihood
No EPSS score yet
Published 3 Nov 2026Analysed here 3 Nov 2026CVSS scored by the publisher (CNA)
common questions

Is CVE-2026-119179 being exploited?

Not confirmed. CVE-2026-119179 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-119179?

CVE-2026-119179 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-119179?

Not known from our data. No patch reference has been recorded for CVE-2026-119179, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-119179 affect?

CVE-2026-119179 affects MongoDB Node.js driver, Node.js backend applications using the driver, MongoDB deployments accessed via Node.js apps. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-119179?

Disable client-side operation timeouts and avoid connection reuse; update driver when vendor releases fix.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MongoDB Node.js driverNode.js backend applications using the driverMongoDB deployments accessed via Node.js apps
impact

Unauthenticated requests can trigger DB replies returned to wrong clients, causing data disclosure, incorrect results, and request failures.

action required

Immediate action required

affected versions
MongoDB Node.js Driver
  • affected>= 6.11.0 and < 6.22.0
  • affected>= 7.0.0 and < 7.8.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

timeline

  1. 3 Nov 2026Published
  2. 3 Nov 2026CVE record last updated · same day later
  3. 3 Nov 2026Analysed by vulneraibility.com · same day later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
1 reference in the CVE record: 1 link

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved