[security - high] nodejs:22 security, bug fix, and enhancement update

エラータID: AXSA:2026-2335:01

Release date: 
Friday, November 20, 2026 - 18:14
Subject: 
[security - high] nodejs:22 security, bug fix, and enhancement update
Affected Channels: 
Asianux Server 8 for x86_64
Severity: 
High
Description: 

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

* brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns (CVE-2026-102278)
* brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns (CVE-2026-102276)
* undici: undici: Denial of Service via unhandled stream error on excessive content encodings (CVE-2026-109869)
* undici: undici: Denial of Service via TLS renegotiation with mismatched certificate (CVE-2026-87018)
* undici: undici: Certificate validation bypass via dropped TLS options in Agent (CVE-2026-109383)
* undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching (CVE-2026-109829)
* nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames (CVE-2026-106069)
* nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character (CVE-2026-105482)

Bug Fix(es) and Enhancement(s):

* nodejs:22/nodejs: Rebase to the latest Node.js 22 release [rhel-8] (JIRA:RHEL-289618)

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.

CVE-2026-102276
The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses push.apply to pass every element of a very large comma-part array as a function argument. Patterns containing many comma-separated brace groups trigger the recursive path, while the large array triggers the argument-array path without deep recursion. These paths cause recursive and argument-array native stack exhaustion before max or maxLength can limit output, potentially terminating the Node.js process in a process-terminating denial of service. This issue is fixed in versions 1.1.19, 2.1.5, 3.0.7, and 5.0.10.
CVE-2026-102278
The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.20, 2.1.6, 3.0.8, and 5.0.11, deeply nested brace groups cause expand_() to recurse once per nesting level at comma-member and single-set expansion sites, exhausting the native stack before output limits can apply and potentially terminating the Node.js process. expand_ performs uncontrolled recursion for nested brace alternatives and single-part sets. deeply nested brace groups supplied as an untrusted pattern. expand_ is affected. expand is affected. Comma members is affected. Single set is affected. native stack exhaustion during nested sub-expansion. process-terminating denial of service. This issue is fixed in versions 1.1.20, 2.1.6, 3.0.8, and 5.0.11.
CVE-2026-105482
A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options. Because the name is passed to c-ares as a C string, resolving attacker.example\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
CVE-2026-106069
A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
CVE-2026-109383
undici is an HTTP client library for Node.js. In versions 4.0.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its Agent dispatcher passes its constructor options through a JSON-based deep clone before forwarding them to each per-origin pool, and because JSON cannot represent functions, a caller-supplied tls option containing a checkServerIdentity callback is silently dropped before it reaches the TLS layer. As a result, a TLS peer whose certificate a custom checkServerIdentity was written to reject, but which passes Node's default hostname and chain checks, is silently accepted. Because Agent is the default dispatcher behind request, fetch, and setGlobalDispatcher, this affects the path most applications use, and EnvHttpProxyAgent is affected on its direct and no-proxy routes as well, while only applications that pass a function-valued tls option such as a custom checkServerIdentity for certificate or public-key pinning are at risk. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, which preserve the tls option outside the JSON clone so custom verification callbacks are forwarded unchanged, and users should upgrade to one of those versions or later. As a workaround, pass the TLS options through connect instead of tls, or for proxied destinations use requestTls and proxyTls.
CVE-2026-109829
undici is an HTTP client library for Node.js. In versions 7.0.0 through 7.30.0 and 8.0.0 through 8.12.1, when an originless Agent composes the redirect and cache interceptors in that order with a shared cache store, the cache builds its key from the original request URL before the redirect handler changes the origin, so a response produced after a cross-origin redirect is stored under the original key. An attacker who controls the target of a redirect from a trusted URL can have their response cached under that trusted URL and served to later callers, allowing persistent cache poisoning, and the same key confusion lets a private, non-stored redirect response to a user-specific resource be stored under the original URL and served to a later unauthenticated caller, disclosing private data. Applications are affected only when an originless Agent, a shared cache store, and the redirect-then-cache composition are all used. The issue is fixed in undici 7.30.1 and 8.12.2, which verify the producing origin still matches the cache key and preserve each redirect hop's cache-control policy before storing, and users should upgrade to one of those versions or later. As a workaround, compose the cache interceptor before the redirect interceptor, use per-origin dispatchers and cache stores, or disable shared caching on redirect-capable requests.
CVE-2026-109869
undici is an HTTP client library for Node.js. In versions 6.23.0 through 6.29.0, 7.18.0 through 7.30.0, and 8.0.0 through 8.12.1, its fetch() implementation crashes the Node.js process when a malicious server returns a response with more than five content codings and closes the connection before sending the body. undici rejects such responses because of a content-encoding limit, but it created the internal response stream before that check and returned without attaching an error listener or aborting the request, so the early close surfaces a content-length mismatch on the orphaned stream, which Node.js treats as an unhandled error and terminates the process. A remote, unauthenticated server can trigger this with a single response, even when the application correctly catches the fetch() rejection, resulting in a denial of service. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. There is no workaround.
CVE-2026-87018
undici is an HTTP client library for Node.js. In versions 4.2.1 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, the client process crashes when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with a certificate-altname error, but undici's established-socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught assertion that terminates the Node.js process, affecting both the HTTP/1.1 and HTTP/2 paths. A malicious or compromised HTTPS endpoint reached through undici or the global fetch() can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process, and exploitation needs no CA compromise because the attacker controls the endpoint and can present two ordinary valid certificates. Only TLS 1.2 is affected, since TLS 1.3 does not support renegotiation. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. As a workaround, restrict outbound connections to TLS 1.3 so renegotiation cannot occur, when the target endpoints support it.

Modularity name: "nodejs"
Stream name: "22"

Solution: 

Update packages.

Additional Info: 

N/A

Download: 

SRPMS
  1. nodejs-nodemon-3.1.14-3.module+el8+2085+357ef821.src.rpm
    MD5: 3fabad3bb3198553efca3501ef0b5125
    SHA-256: 42e4abbf433712b04761afff2d0280059c64a79093907bf2064fc943684de8f1
    Size: 470.46 kB
  2. nodejs-packaging-2021.06-6.module+el8+2085+357ef821.src.rpm
    MD5: bdf1d7f8a64fbb6f02bc3e2c16c1d85c
    SHA-256: 07c6b9fd63ab62e251baca7c0cf5a60d1245a8f00cbded9a424c090e51473c2d
    Size: 30.99 kB
  3. nodejs-22.23.4-2.module+el8+2085+357ef821.src.rpm
    MD5: 1e271f3af23a71972cc7ad3b719f5b4c
    SHA-256: 21c7b01788c211b3f2389d9a811cf018635181df231fa7ffbe1595e93d8d7b98
    Size: 95.14 MB

Asianux Server 8 for x86_64
  1. nodejs-22.23.4-2.module+el8+2085+357ef821.x86_64.rpm
    MD5: 5921f6e7f7c86b7b5e3a7ad267b8da38
    SHA-256: c230c1bff9d365862b8faf61ad3014207d3a72f7a43fe1ee4d13c6c40a4dfb21
    Size: 2.00 MB
  2. nodejs-debugsource-22.23.4-2.module+el8+2085+357ef821.x86_64.rpm
    MD5: 54e2e4100ba5c85dae4828904bf32ea7
    SHA-256: bbfe9db11ec84a2f1bc9266c1f35a158a8b39afc6e6721fc9148530856a5d472
    Size: 20.02 MB
  3. nodejs-devel-22.23.4-2.module+el8+2085+357ef821.x86_64.rpm
    MD5: f275d65f8fd6da87444255947a992d1f
    SHA-256: 6f46b54371a1dd9bb3806a9725be2db8cb549b60d4a4f2b0515d065b0ff4af74
    Size: 270.35 kB
  4. nodejs-docs-22.23.4-2.module+el8+2085+357ef821.noarch.rpm
    MD5: 3b3c14e32d1a78d47fe23d6611015b5a
    SHA-256: 938ade58a85b8b4166612bf7a400d1f98c051f52c03a36c65a178fa014cdd8bf
    Size: 11.70 MB
  5. nodejs-full-i18n-22.23.4-2.module+el8+2085+357ef821.x86_64.rpm
    MD5: 3f24dd5c991082ca1f597ac2dae55e91
    SHA-256: e7a6daa0142f2b5d093dbc12104571e17f50a58724b9d13ba4a93079b453a485
    Size: 8.60 MB
  6. nodejs-libs-22.23.4-2.module+el8+2085+357ef821.x86_64.rpm
    MD5: 36354faac2678c6d98988f96b92c847b
    SHA-256: cbd72bd930f76afb0a19f47acfef6e56be1f00234c44a349f4fa344153398bfa
    Size: 20.72 MB
  7. nodejs-nodemon-3.1.14-3.module+el8+2085+357ef821.noarch.rpm
    MD5: 4f9c30415b5d443bf0ec09ddb03d65fd
    SHA-256: 856624d3d31f420c3f6fe1840f7f817bbb092b91303ebd88d5c52ce2fec02c45
    Size: 323.43 kB
  8. nodejs-packaging-2021.06-6.module+el8+2085+357ef821.noarch.rpm
    MD5: b4cb33fcba326d5196b4365557e968ae
    SHA-256: ac0a93f65177b102cebc5dfae3009bc650a9823fb106701708042468d832d0bb
    Size: 24.51 kB
  9. nodejs-packaging-bundler-2021.06-6.module+el8+2085+357ef821.noarch.rpm
    MD5: 656042d7fa73317226c9dc06b2f9b271
    SHA-256: e75009f08234026dafe6ac9b3d7fc4ca12d71521692b2588ac9b149053f1ad1a
    Size: 14.09 kB
  10. npm-10.9.9-1.22.23.4.2.module+el8+2085+357ef821.x86_64.rpm
    MD5: 77595b3e94d64dc16f034211cdb4a925
    SHA-256: 422dbab252c4abad600cb52974bab2689f4da90ade99735be980b727cee2853b
    Size: 2.17 MB
  11. v8-12.4-devel-12.4.254.21-1.22.23.4.2.module+el8+2085+357ef821.x86_64.rpm
    MD5: 8004f441009abb25a1e28730d2630c2a
    SHA-256: 1ba2c289d8a06ba0adf519051f85c137b5394e1952c5b99ed1fdc5115d20aeb2
    Size: 16.70 kB