Summary
Node.js is a platform built on Chrome's JavaScript runtime \ for easily building fast, scalable network applications. \ Node.js uses an event-driven, non-blocking I/O model that \ makes it lightweight and efficient, perfect for data-intensive \ real-time applications that run across distributed devices.
Security Fix(es):
* ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
* undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
* undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
* undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
* undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
* nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
* nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
* nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
* nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
* nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
* Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
* nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
* nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
* nodejs22: Rebase to the latest Node.js 22 release [almalinux-10.2.z] (JIRA:AlmaLinux-186623)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Fixed packages 6
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 10 | nodejs | 1:22.23.1-2.el10_2 |
| AlmaLinux · 10 | nodejs-devel | 1:22.23.1-2.el10_2 |
| AlmaLinux · 10 | nodejs-docs | 1:22.23.1-2.el10_2 |
| AlmaLinux · 10 | nodejs-full-i18n | 1:22.23.1-2.el10_2 |
| AlmaLinux · 10 | nodejs-libs | 1:22.23.1-2.el10_2 |
| AlmaLinux · 10 | nodejs-npm | 1:10.9.8-1.22.23.1.2.el10_2 |
Vulnerabilities 16
-
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
A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2G…
-
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.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://access.redhat.com/security/cve/CVE-2026-11525
-
report
https://access.redhat.com/security/cve/CVE-2026-12151
-
report
https://access.redhat.com/security/cve/CVE-2026-42338
-
report
https://access.redhat.com/security/cve/CVE-2026-48615
-
report
https://access.redhat.com/security/cve/CVE-2026-48618
-
report
https://access.redhat.com/security/cve/CVE-2026-48619
-
report
https://access.redhat.com/security/cve/CVE-2026-48928
-
report
https://access.redhat.com/security/cve/CVE-2026-48930
-
report
https://access.redhat.com/security/cve/CVE-2026-48933
-
report
https://access.redhat.com/security/cve/CVE-2026-48934
-
report
https://access.redhat.com/security/cve/CVE-2026-48935
-
report
https://access.redhat.com/security/cve/CVE-2026-6733
-
report
https://access.redhat.com/security/cve/CVE-2026-9678
-
report
https://bugzilla.redhat.com/2476810
-
report
https://bugzilla.redhat.com/2489980
-
report
https://bugzilla.redhat.com/2490000
-
report
https://bugzilla.redhat.com/2490006
-
report
https://bugzilla.redhat.com/2490008
-
report
https://bugzilla.redhat.com/2493325
-
report
https://bugzilla.redhat.com/2493326
-
report
https://bugzilla.redhat.com/2493329
-
report
https://bugzilla.redhat.com/2493331
-
report
https://bugzilla.redhat.com/2493332
-
report
https://bugzilla.redhat.com/2493333
-
report
https://bugzilla.redhat.com/2493335
-
report
https://bugzilla.redhat.com/2493337
-
advisory
https://errata.almalinux.org/10/ALSA-2026-35842.html
-
report
https://www.redhat.com/security/data/cve/CVE-2026-48617.html
-
report
https://www.redhat.com/security/data/cve/CVE-2026-48931.html
-
report
https://www.redhat.com/security/data/cve/CVE-2026-48937.html