nodejs:22 security, bug fix, and enhancement update
エラータID: AXSA:2026-1453:01
リリース日:
2026/08/05 Wednesday - 03:33
題名:
nodejs:22 security, bug fix, and enhancement update
影響のあるチャネル:
Asianux Server 8 for x86_64
Severity:
High
Description:
以下項目について対処しました。
[Security Fix]
- Node.js の undici には、リモートの攻撃者により、巧妙に細工
された Set-Cookie ヘッダの送信を介して、情報の漏洩、およびデータ
破壊を可能とする脆弱性が存在します。(CVE-2026-11525)
- Node.js の undici には、リソースの制限を実施していない問題
があるため、リモートの攻撃者により、サービス拒否攻撃 (DoS) を
可能とする脆弱性が存在します。(CVE-2026-12151)
- JavaScript の ip-address ライブラリには、リモートの攻撃者
により、クロスサイトスクリプティング攻撃を可能とする脆弱性が
存在します。(CVE-2026-42338)
- Node.js には、エラーメッセージに意図しない情報を出力してしまう
問題があるため、リモートの攻撃者により、エラーメッセージからの情報
の漏洩を可能とする脆弱性が存在します。(CVE-2026-48615)
- Node.js には、認証を回避できてしまう問題があるため、リモートの
攻撃者により、情報の漏洩を可能とする脆弱性が存在します。
(CVE-2026-48618)
- Node.js には、リソースの制限を実施していない問題があるため、
リモートの攻撃者により、サービス拒否攻撃 (DoS) を可能とする脆弱性
が存在します。(CVE-2026-48619)
- Node.js には、認証を回避できてしまう問題があるため、リモートの
攻撃者により、情報の漏洩、およびデータ破壊を可能とする脆弱性が存在
します。(CVE-2026-48928)
- Node.js には、TLS の処理においてホスト名に NULL が埋め込まれる
ことを許容してしまう問題があるため、リモートの攻撃者により、情報
の漏洩、データ破壊、およびサービス拒否攻撃を可能とする脆弱性が存在
します。(CVE-2026-48930)
- Node.js の WebCrypto の実装には、リソースの制限を実施していない
問題があるため、リモートの攻撃者により、サービス拒否攻撃 (DoS) を
可能とする脆弱性が存在します。(CVE-2026-48933)
- Node.js には、証明書の検証処理に問題があるため、リモートの
攻撃者により、不正な認証を可能とする脆弱性が存在します。
(CVE-2026-48934)
- Node.js の Permission API には、ローカルの攻撃者により、
データ破壊を可能とする脆弱性が存在します。(CVE-2026-48935)
- Undici の HTTP/1.1 クライアントには、リモートの攻撃者により、
データ破壊を可能とする脆弱性が存在します。(CVE-2026-6733)
- undici には、リモートの攻撃者により、情報の漏洩を可能とする
脆弱性が存在します。(CVE-2026-9678)
Modularity name: nodejs
Stream name: 22
解決策:
パッケージをアップデートしてください。
CVE:
CVE-2026-11525
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 three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict). Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide. This was introduced in undici 5.15.0 when the cookies feature was added. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
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 three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict). Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide. This was introduced in undici 5.15.0 when the cookies feature was added. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
CVE-2026-12151
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 each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (new WebSocket(...)) or the WebSocketStream API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. All releases starting at undici 6.17.0 are affected. Patches: Upgrade to undici >= 6.26.0, >= 7.28.0, or >= 8.5.0. Workarounds: No workaround is available. The fix must be applied through an upgrade.
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 each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (new WebSocket(...)) or the WebSocketStream API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. All releases starting at undici 6.17.0 are affected. Patches: Upgrade to undici >= 6.26.0, >= 7.28.0, or >= 8.5.0. Workarounds: No workaround is available. The fix must be applied through an upgrade.
CVE-2026-42338
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 AddressError.parseMessage (emitted by the Address6 constructor for invalid input) can contain unescaped attacker-controlled content in one branch. An application that (1) passes untrusted input to Address6 and (2) renders the output of these methods, or the thrown error's parseMessage, as HTML (e.g. via innerHTML) is vulnerable to cross-site scripting. This vulnerability is fixed in 10.1.1.
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 AddressError.parseMessage (emitted by the Address6 constructor for invalid input) can contain unescaped attacker-controlled content in one branch. An application that (1) passes untrusted input to Address6 and (2) renders the output of these methods, or the thrown error's parseMessage, as HTML (e.g. via innerHTML) is vulnerable to cross-site scripting. This vulnerability is fixed in 10.1.1.
CVE-2026-48615
A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embedded in the proxy URL, they may be exposed through error handling paths and captured by logs, diagnostics, or other error consumers. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embedded in the proxy URL, they may be exposed through error handling paths and captured by logs, diagnostics, or other error consumers. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-48618
A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-48619
A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-48928
A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-48930
A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-48933
A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-48934
A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-48935
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 e.g. `--allow-fs-read`. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
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 e.g. `--allow-fs-read`. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-6733
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 dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool.
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 dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool.
CVE-2026-9678
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 parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored. In shared-cache mode, this allows a response containing one user's authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key. Affected applications are those that explicitly enable the cache interceptor (interceptors.cache()) in shared mode, forward Authorization headers upstream, and receive cacheable responses with non-canonical qualified private or no-cache directives. Patches: Upgrade to undici v7.28.0 or v8.5.0. Workarounds: If upgrade is not immediately possible, disable shared-cache mode for traffic that includes Authorization headers, avoid caching responses to authenticated requests, or add Vary: Authorization upstream.
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 parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored. In shared-cache mode, this allows a response containing one user's authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key. Affected applications are those that explicitly enable the cache interceptor (interceptors.cache()) in shared mode, forward Authorization headers upstream, and receive cacheable responses with non-canonical qualified private or no-cache directives. Patches: Upgrade to undici v7.28.0 or v8.5.0. Workarounds: If upgrade is not immediately possible, disable shared-cache mode for traffic that includes Authorization headers, avoid caching responses to authenticated requests, or add Vary: Authorization upstream.
追加情報:
N/A
ダウンロード:
SRPMS
- nodejs-nodemon-3.0.1-1.module+el8+2013+a3d7836c.src.rpm
MD5: 940e35fed94f378ccce15cd0bd764434
SHA-256: f46f2420148e89a1101161d65d52f3aa590392f53138eca9d8722ff8a40ac1d7
Size: 340.07 kB - nodejs-packaging-2021.06-6.module+el8+2013+a3d7836c.src.rpm
MD5: 491d57cf40b7308ad860670a4efc7d66
SHA-256: c30fb79d393acd6c8fdeed4ed8b674cf08f7dd22418272577c1be7f743b01d2a
Size: 30.99 kB - nodejs-22.23.1-1.module+el8+2013+a3d7836c.src.rpm
MD5: 90840bb24680d92e308d4d2f00410ff3
SHA-256: 153b55ad3095b33927bf2915bc7d74265cd82327f9dab440cb6c9296aad6861d
Size: 95.22 MB
Asianux Server 8 for x86_64
- nodejs-22.23.1-1.module+el8+2013+a3d7836c.x86_64.rpm
MD5: 94da8bd5cfa9b0e58c6b8de348d241cb
SHA-256: fa880f3947d9363a1bfb71128650403c82f2cd2e58344bcd304092abd3e62e12
Size: 1.98 MB - nodejs-debugsource-22.23.1-1.module+el8+2013+a3d7836c.x86_64.rpm
MD5: 59289d46fb3d28cf9d8a5d4358af646c
SHA-256: dc6fc1fd3d72b25bcde7bab8baaf3f32221a5772f32a701dea56db4ad32816a7
Size: 19.95 MB - nodejs-devel-22.23.1-1.module+el8+2013+a3d7836c.x86_64.rpm
MD5: 7c373cc5a6838125defdf475183deb60
SHA-256: fafe5a714e3385a36334481702069d5ea791f42599d895e77a0a14085c199843
Size: 269.05 kB - nodejs-docs-22.23.1-1.module+el8+2013+a3d7836c.noarch.rpm
MD5: a93866aaa977affee4520ec546eae69d
SHA-256: cf9f14bffbf03252ccecfa1a9c78bffa6526031a02207683567b55b079afe837
Size: 11.69 MB - nodejs-full-i18n-22.23.1-1.module+el8+2013+a3d7836c.x86_64.rpm
MD5: 95a96aacfcc10aed0ee54ebeb8b64599
SHA-256: 82596458c63ab5e87e91d743268d1b62ea7323427b1b838128e63b2068b296b3
Size: 8.60 MB - nodejs-libs-22.23.1-1.module+el8+2013+a3d7836c.x86_64.rpm
MD5: 28617552cad6b8f346c24b73aa6ab42e
SHA-256: a8b1ec66af546b9fb8ea2c2e5953bb11ad7368fd23c52a30e448dfc364e18f81
Size: 20.72 MB - nodejs-nodemon-3.0.1-1.module+el8+2013+a3d7836c.noarch.rpm
MD5: 55b057ed74a58479c5d258b9dae0ca73
SHA-256: 2b370cf3d1570a4d8ae065fe52645af388331095dcbe5da1004297a54cede118
Size: 281.66 kB - nodejs-packaging-2021.06-6.module+el8+2013+a3d7836c.noarch.rpm
MD5: cbc1bdac8655888b27a09382b246d7bd
SHA-256: 1b18b1cdb86f019a92ad3ce1e247610abc3e47e40101a8c29be58d360da1dc3b
Size: 24.51 kB - nodejs-packaging-bundler-2021.06-6.module+el8+2013+a3d7836c.noarch.rpm
MD5: 9fe69d403dfa131d48fd7d9b07272ed7
SHA-256: ccf9feb3c3c68901c15640d9477d8c4effae23e999ace468f8c2332a5a08cb03
Size: 14.10 kB - npm-10.9.8-1.22.23.1.1.module+el8+2013+a3d7836c.x86_64.rpm
MD5: bc3899def82aa754f72f246ce11e9ccc
SHA-256: 50e48316e8c793c161cf738cb8d2ac4cb1ae6689803716b65248d258543065d8
Size: 2.15 MB - v8-12.4-devel-12.4.254.21-1.22.23.1.1.module+el8+2013+a3d7836c.x86_64.rpm
MD5: 5e98e614088d07e1c488fcd62cd1eefb
SHA-256: 9cc33934e35bf31eb5a9c16abb631753d061cafc7eacc68331aff09fabf4c83c
Size: 15.48 kB
English