rpm package
opensuse/nodejs24&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/nodejs24&distro=openSUSE%20Tumbleweed
Vulnerabilities (91)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-126051 | Hig | 7.5 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A deferred-callback use-after-destroy in Node.js TLS server handshake handling allows a remote, unauthenticated attacker to terminate the server process. When a TLS server uses any of the SNICallback, OCSPRequest, newSession, or resumeSession hooks, or server.addContext(), the co | |
| CVE-2026-123877 | Med | 6.8 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one | |
| CVE-2026-123875 | Med | 5.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A NULL pointer dereference in Node.js HTTP/2 lets an unauthenticated client crash the server, over both TLS and cleartext, by cancelling file downloads. When the server serves a file with stream.respondWithFile() or stream.respondWithFD() and the client cancels the request, a Str | |
| CVE-2026-123874 | Hig | 7.5 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | 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 i | |
| CVE-2026-123872 | Hig | 8.1 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only cl | |
| CVE-2026-123871 | Med | 6.2 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the | |
| CVE-2026-123868 | Med | 5.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that que | |
| CVE-2026-123867 | Med | 4.2 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` | |
| CVE-2026-123866 | Hig | 7.5 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server's own per-stre | |
| CVE-2026-123865 | Hig | 7.5 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never no | |
| CVE-2026-123864 | Hig | 8.1 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScrip | |
| CVE-2026-123863 | Hig | 8.2 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the | |
| CVE-2026-123862 | Low | 2.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer | |
| CVE-2026-123829 | Low | 2.5 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A Permission Model bypass in Node.js recursive file watching discloses the names of files and directories the process is not permitted to read. On macOS and Windows, fs.watch() and fs.promises.watch() in recursive mode are backed by the native libuv watcher: FSEventWrap::Start ch | |
| CVE-2026-123828 | Med | 5.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 11, 2026 | A one-byte heap buffer overflow in Node.js HTTP/2 Alt-Svc handling lets a remote, unauthenticated attacker corrupt process memory. When an application passes an attacker-controlled value such as a request's :authority header to Http2Session.altsvc(), the AltSvc implementation in | |
| CVE-2026-116630 | Med | 5.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 6, 2026 | undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when an Agent composes the redirect and shared cache interceptors, a cached response that is revalidated with a conditional request can be validated by a 304 Not Modified from a diffe | |
| CVE-2026-120474 | Med | 6.5 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 6, 2026 | undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when the redirect interceptor and a shared response cache are used together, an authenticated request that is redirected to a same-origin target has the final response stored under th | |
| CVE-2026-120423 | Med | 5.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 6, 2026 | undici is an HTTP client for Node.js. In versions 7.15.0 through 7.30.1 and 8.0.0 through 8.12.3, fetch verifies Subresource Integrity metadata by splitting the integrity string on a single space, but the SRI grammar separates metadata by ASCII whitespace, which also includes the | |
| CVE-2026-120415 | Med | 5.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 6, 2026 | undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, the redirect interceptor strips sensitive headers such as Authorization, Cookie, Proxy-Authorization, and Host when a request is redirected to a different origin, but when request hea | |
| CVE-2026-120222 | Med | 5.9 | < 24.22.3-1.1 | 24.22.3-1.1 | Nov 6, 2026 | undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when the cache interceptor is composed with a downstream handler that throws during response processing (such as the built-in dump interceptor exceeding its maxSize, or the decompress |
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A deferred-callback use-after-destroy in Node.js TLS server handshake handling allows a remote, unauthenticated attacker to terminate the server process. When a TLS server uses any of the SNICallback, OCSPRequest, newSession, or resumeSession hooks, or server.addContext(), the co
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A NULL pointer dereference in Node.js HTTP/2 lets an unauthenticated client crash the server, over both TLS and cleartext, by cancelling file downloads. When the server serves a file with stream.respondWithFile() or stream.respondWithFD() and the client cancels the request, a Str
- affected < 24.22.3-1.1fixed 24.22.3-1.1
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 i
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only cl
- affected < 24.22.3-1.1fixed 24.22.3-1.1
Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the
- affected < 24.22.3-1.1fixed 24.22.3-1.1
An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that que
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })`
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server's own per-stre
- affected < 24.22.3-1.1fixed 24.22.3-1.1
An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never no
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScrip
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the
- affected < 24.22.3-1.1fixed 24.22.3-1.1
An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A Permission Model bypass in Node.js recursive file watching discloses the names of files and directories the process is not permitted to read. On macOS and Windows, fs.watch() and fs.promises.watch() in recursive mode are backed by the native libuv watcher: FSEventWrap::Start ch
- affected < 24.22.3-1.1fixed 24.22.3-1.1
A one-byte heap buffer overflow in Node.js HTTP/2 Alt-Svc handling lets a remote, unauthenticated attacker corrupt process memory. When an application passes an attacker-controlled value such as a request's :authority header to Http2Session.altsvc(), the AltSvc implementation in
- affected < 24.22.3-1.1fixed 24.22.3-1.1
undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when an Agent composes the redirect and shared cache interceptors, a cached response that is revalidated with a conditional request can be validated by a 304 Not Modified from a diffe
- affected < 24.22.3-1.1fixed 24.22.3-1.1
undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when the redirect interceptor and a shared response cache are used together, an authenticated request that is redirected to a same-origin target has the final response stored under th
- affected < 24.22.3-1.1fixed 24.22.3-1.1
undici is an HTTP client for Node.js. In versions 7.15.0 through 7.30.1 and 8.0.0 through 8.12.3, fetch verifies Subresource Integrity metadata by splitting the integrity string on a single space, but the SRI grammar separates metadata by ASCII whitespace, which also includes the
- affected < 24.22.3-1.1fixed 24.22.3-1.1
undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, the redirect interceptor strips sensitive headers such as Authorization, Cookie, Proxy-Authorization, and Host when a request is redirected to a different origin, but when request hea
- affected < 24.22.3-1.1fixed 24.22.3-1.1
undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when the cache interceptor is composed with a downstream handler that throws during response processing (such as the built-in dump interceptor exceeding its maxSize, or the decompress
Page 1 of 5