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.
Thu, 12 Nov 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs nodejs |
|
| Vendors & Products |
Nodejs
Nodejs nodejs |
Thu, 12 Nov 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-825 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Wed, 11 Nov 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0). | |
| Title | Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write | |
| Weaknesses | CWE-416 | |
| References |
| |
| Metrics |
cvssV3_0
|
Status: PUBLISHED
Assigner: openjs
Published:
Updated: 2026-11-11T18:32:20.292Z
Reserved: 2026-11-06T16:21:26.084Z
Link: CVE-2026-123874
No data.
Status : Awaiting Analysis
Published: 2026-11-11T19:17:34.490
Modified: 2026-11-12T19:02:35.830
Link: CVE-2026-123874
OpenCVE Enrichment
Updated: 2026-11-12T18:30:06Z