Summary
This update for nodejs24 fixes the following issues
Update to 24.17.0:
- CVE-2026-2581: undici: Undici: Denial of Service due to uncontrolled resource consumption (bsc#1268480).
- CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response
delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in `addGitSha` when processing a specially crafted `spec.rawSpec`
value can lead to DoS (bsc#1266318).
- CVE-2026-9678: undici: Undici: Information disclosure due to improper cache-control header parsing (bsc#1268478).
- CVE-2026-9679: undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding (bsc#1268477).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header
(bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog parameters_set stack buffer overflow (bsc#1262274).
- CVE-2026-42338: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: Proxy credentials leaked in ERR_PROXY_TUNNEL error message (bsc#1268598).
- CVE-2026-48617: permission model enforcement bypass via `process.report.writeReport()` path misvalidation
(bsc#1268554).
- CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to
resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname
matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver
bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to
unauthorized connections (bsc#1268608).
- CVE-2026-48935: Permission Model bypass via FileHandle.utimes() in the promises API (bsc#1268609).
- CVE-2026-48937: servers keep accepting data even after sending a `GOAWAY` frame (bsc#1268555).
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 15 SP7 Linux Enterprise Module for Web and Scripting 15 SP7 | nodejs24 | 24.17.0-150700.15.11.1 |
Vulnerabilities 21
-
High 7.7
A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth…
-
High 7.5
undici WebSocket client vulnerable to denial of service via fragment count bypass
Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that ea…
-
High 7.5
nghttp2 Denial of service: Assertion failure due to the missing state validation
nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. Prior to version 1.68.1, the nghttp2 library stops reading the incoming data when user facing public API `nghttp2_session_terminate_session` or `nghttp2_session_terminate_session2…
-
High 7.5
ngtcp2 has a qlog transport parameter serialization stack buffer overflow
ngtcp2 is a C implementation of the IETF QUIC protocol. In versions prior to 1.22.1, ngtcp2_qlog_parameters_set_transport_params() serializes peer transport parameters into a fixed 1024-byte stack buffer without bounds checking. When qlog is enabled, a remote…
-
High 7.5
A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2G…
-
High 7.5
pacote is vulnerable to Denial of Service (DoS) via the addGitSha function
Versions of the package pacote from 11.2.7 and before 21.5.1 are vulnerable to Denial of Service (DoS) via the addGitSha function. An attacker can exploit this vulnerability by supplying a specially crafted spec.rawSpec value that triggers the function’s rege…
-
Medium 5.9
undici is vulnerable to Unbounded Memory Consumption in in Undici's DeduplicationHandler via Response Buffering leads to DoS
This is an uncontrolled resource consumption vulnerability (CWE-400) that can lead to Denial of Service (DoS). In vulnerable Undici versions, when interceptors.deduplicate() is enabled, response data for deduplicated requests could be accumulated in memory fo…
-
Medium 5.9
A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When…
-
Medium 5.9
undici vulnerable to cross-user information disclosure via shared cache whitespace bypass
Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The p…
-
Medium 5.9
undici vulnerable to HTTP header injection via Set-Cookie percent-decoding
Impact: undici's cookie parser in parseSetCookie percent-decodes cookie values via qsUnescape, turning encoded sequences like %0D%0A, %00, %3B, and %3D into their literal byte equivalents. RFC 6265 §5.4 does not specify any decoding and browsers do not decode…
-
Medium 5.6
A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to …
-
Medium 5.3
ip-address: XSS in Address6 HTML-emitting methods
ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.1.1, Address6.group() and Address6.link() do not HTML-escape attacker-controlled content before embedding it in the HTML strings they return, and AddressEr…
-
Medium 5.3
A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Ou…
-
Medium 5.3
A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. This …
-
Medium 4.3
A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability af…
-
Medium 4.2
A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnera…
-
Low 3.7
undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the th…
-
Low 3.7
A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client has sent t…
-
Low 3.7
undici vulnerable to HTTP response queue poisoning via keep-alive socket reuse
Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatch…
-
Low 3.3
A flaw in Node.js Permission API can cause a file metadata to be modified even on a path that was set as read-only with…
-
Low 1.8
A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. Thi…
References
-
report
https://bugzilla.suse.com/1259853
-
report
https://bugzilla.suse.com/1262274
-
report
https://bugzilla.suse.com/1266318
-
report
https://bugzilla.suse.com/1268097
-
report
https://bugzilla.suse.com/1268477
-
report
https://bugzilla.suse.com/1268478
-
report
https://bugzilla.suse.com/1268479
-
report
https://bugzilla.suse.com/1268480
-
report
https://bugzilla.suse.com/1268481
-
report
https://bugzilla.suse.com/1268482
-
report
https://bugzilla.suse.com/1268554
-
report
https://bugzilla.suse.com/1268555
-
report
https://bugzilla.suse.com/1268592
-
report
https://bugzilla.suse.com/1268593
-
report
https://bugzilla.suse.com/1268598
-
report
https://bugzilla.suse.com/1268605
-
report
https://bugzilla.suse.com/1268606
-
report
https://bugzilla.suse.com/1268608
-
report
https://bugzilla.suse.com/1268609
-
report
https://bugzilla.suse.com/1268611
-
report
https://bugzilla.suse.com/1268618
-
web
https://www.suse.com/security/cve/CVE-2026-11525
-
web
https://www.suse.com/security/cve/CVE-2026-12151
-
web
https://www.suse.com/security/cve/CVE-2026-2581
-
web
https://www.suse.com/security/cve/CVE-2026-27135
-
web
https://www.suse.com/security/cve/CVE-2026-40170
-
web
https://www.suse.com/security/cve/CVE-2026-42338
-
web
https://www.suse.com/security/cve/CVE-2026-48615
-
web
https://www.suse.com/security/cve/CVE-2026-48617
-
web
https://www.suse.com/security/cve/CVE-2026-48618
-
web
https://www.suse.com/security/cve/CVE-2026-48619
-
web
https://www.suse.com/security/cve/CVE-2026-48928
-
web
https://www.suse.com/security/cve/CVE-2026-48930
-
web
https://www.suse.com/security/cve/CVE-2026-48931
-
web
https://www.suse.com/security/cve/CVE-2026-48933
-
web
https://www.suse.com/security/cve/CVE-2026-48934
-
web
https://www.suse.com/security/cve/CVE-2026-48935
-
web
https://www.suse.com/security/cve/CVE-2026-48937
-
web
https://www.suse.com/security/cve/CVE-2026-6733