nodejs:24 security update
エラータID: AXSA:2026-2329:01
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)
* sqlite: sqlite: Denial of service via heap-based buffer overflow in FTS5 (CVE-2026-119373)
* sqlite: sqlite: Arbitrary code execution via crafted session changesets (CVE-2026-119379)
* sqlite: sqlite: Arbitrary code execution via corrupted FTS5 index (CVE-2026-119374)
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-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-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-119373
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5MergeRowidLists() that undersizes the output buffer when merging detail=none prefix doclists. Attackers who can populate a detail=none FTS5 table with negative rowids and run a prefix MATCH query can write past the allocation, corrupting heap memory and crashing the process.
CVE-2026-119374
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application.
CVE-2026-119379
SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation.
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: "24"
Update packages.
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.
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.
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.
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.
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5MergeRowidLists() that undersizes the output buffer when merging detail=none prefix doclists. Attackers who can populate a detail=none FTS5 table with negative rowids and run a prefix MATCH query can write past the allocation, corrupting heap memory and crashing the process.
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application.
SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation.
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.
N/A
SRPMS
- nodejs-nodemon-3.1.14-2.module+el8+2082+d1c03150.src.rpm
MD5: 0c84152610a1817c0f6659d621c66c9d
SHA-256: d976e934239c9242d0296b8cd03f6acd4bcdc30913b1f5ab47de16d3d99dddeb
Size: 462.03 kB - nodejs-packaging-2021.06-6.module+el8+2082+d1c03150.src.rpm
MD5: a868996b0f277ef0dfcd1481c9a17afc
SHA-256: 9bccd311e69fc4c2303ce2d6df153c3dc74d3bda1660ab5fe1775c300b1af9e9
Size: 30.68 kB - nodejs-24.22.1-2.module+el8+2082+d1c03150.src.rpm
MD5: b0432309df92a49b0f9c1343fa2a09b8
SHA-256: 707d3ca3c80c2d71c6dcd8f2bf30a4d6881ae5ed5952380f472d437ecbc86970
Size: 102.25 MB
Asianux Server 8 for x86_64
- nodejs-24.22.1-2.module+el8+2082+d1c03150.x86_64.rpm
MD5: 257053e6e807a5d5aad879dc8b879143
SHA-256: 6cdf1a55372ace1014e02aa8070cf5d67d8968cb65cd48a1b7e061415979eb71
Size: 71.15 kB - nodejs-debugsource-24.22.1-2.module+el8+2082+d1c03150.x86_64.rpm
MD5: 3c59b8839a456be2137600e092ebce20
SHA-256: d4d7819d17c8a24d37d5ade9f0d0c5236814878b3044c65416ab2c563a424bd5
Size: 24.19 MB - nodejs-devel-24.22.1-2.module+el8+2082+d1c03150.x86_64.rpm
MD5: c6d1924b3d42e1dc56d26ab7e9fcc905
SHA-256: 3819dc21c63b2c5386da0219c9c62e9cae9f03e84c4f3af3abd29822ebbd342e
Size: 334.05 kB - nodejs-docs-24.22.1-2.module+el8+2082+d1c03150.noarch.rpm
MD5: 43585e2279f00d30614c0295e66abaaf
SHA-256: 06acac7929996221be492b143a6760a1e4cdbbc420edd2c8186bf66c74094916
Size: 6.66 MB - nodejs-full-i18n-24.22.1-2.module+el8+2082+d1c03150.x86_64.rpm
MD5: 63cbd8bd1f094219e034157304f22c90
SHA-256: 656e5a5424d051dd7c44ddcb659829db4dd46d6f83b6fde32e452a4858937252
Size: 8.61 MB - nodejs-libs-24.22.1-2.module+el8+2082+d1c03150.x86_64.rpm
MD5: 70d1450e7bd7ef5bd24f8ac073dcb826
SHA-256: 44cfeeb61bc78a039e7cb29e2d29ca662bcbb0b30698a91d21ffc67dce8143fd
Size: 24.75 MB - nodejs-nodemon-3.1.14-2.module+el8+2082+d1c03150.noarch.rpm
MD5: d4b3b1f9a2f5d4183089598ce4834f02
SHA-256: 6dff0984a8cdbfe4f8349451bb5d2546d83792732bad6b8f977f3048b66ab912
Size: 321.26 kB - nodejs-packaging-2021.06-6.module+el8+2082+d1c03150.noarch.rpm
MD5: 4c4f071a37e7c7a524cb8d4d74027861
SHA-256: 55882efaa8a5512ade153db5cbdac6c27ac5368683044748d55bd0fe1c57eb44
Size: 24.41 kB - nodejs-packaging-bundler-2021.06-6.module+el8+2082+d1c03150.noarch.rpm
MD5: af9875311c43f9fcf7c92fe07e913358
SHA-256: 8121703386a8e97c44a3ec069a62d49d9da3e1c356fde4de3e90c954042e5484
Size: 13.99 kB - npm-11.19.1-1.24.22.1.2.module+el8+2082+d1c03150.noarch.rpm
MD5: 9d2feaef00b9730c7a07007c855814ff
SHA-256: 1d71dd0a60317095970cd983f84035138e857688ce9c8dc38d534029362cbb88
Size: 2.34 MB - v8-13.6-devel-13.6.233.17-1.24.22.1.2.module+el8+2082+d1c03150.x86_64.rpm
MD5: 1244fb4df58514b719a72616d6ecf068
SHA-256: 0f7978843ffd22d6ec3108157ada64654c7c222592e32a76d4b59b65f495aaff
Size: 34.23 kB