Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://jira.mongodb.org/browse/NODE-7958 |
|
Tue, 03 Nov 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 03 Nov 2026 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MongoDB Node.js driver: Connection pool desynchronization after operation timeout can expose other user's data | |
| Weaknesses | CWE-226 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: mongodb
Published:
Updated: 2026-11-03T18:17:31.329Z
Reserved: 2026-10-29T15:43:24.830Z
Link: CVE-2026-119179
Updated: 2026-11-03T18:17:26.854Z
Status : Awaiting Analysis
Published: 2026-11-03T14:17:33.617
Modified: 2026-11-03T19:17:56.150
Link: CVE-2026-119179
No data.
OpenCVE Enrichment
Updated: 2026-11-03T14:30:08Z