Node.js — программная платформа, основанная на движке V8 (компилирующем JavaScript в машинный код)

An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and ` ...

A memory leak occurs in Node.js HTTP/2 servers when a client sends WIN ...

A flaw in Node.js URL processing causes an assertion failure in native ...

A flaw in Node.js HTTP request handling causes an uncaught `TypeError` ...

A flaw in Node.js HMAC verification uses a non-constant-time compariso ...

A flaw in Node.js Permission Model filesystem enforcement leaves `fs.r ...

A flaw in Node.js Permission Model network enforcement leaves Unix Dom ...

A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 2³¹-1. The server correctly sends a GOAWAY frame, but the Http2Session object is never cleaned up. This vulnerability affects HTTP2 users on Node.js 20, 22, 24 and 25.

A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`. When this occurs, `dest["__proto__"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`. * This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x**

A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission checks, while all comparable network paths correctly enforce them. As a result, code running under `--permission` without `--allow-net` can create and expose local IPC endpoints, allowing communication with other processes on the same host outside of the intended network restriction boundary. This vulnerability affects Node.js **25.x** processes using the Permission Model where `--allow-net` is intentionally omitted to restrict network access. Note that `--allow-net` is currently an experimental feature.