Red Hat Security Advisory: nodejs26 security, bug fix, and enhancement update
🔗 CVE IDs covered (31)
📋 Description
CVE-2026-13697 — undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives
CVE-2026-48615 — nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling
CVE-2026-48617 — nodejs: Node.js: Permission Model bypass via process.report.writeReport() path misvalidation
CVE-2026-48618 — nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch
CVE-2026-48619 — nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames
CVE-2026-48928 — Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency
CVE-2026-48930 — nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling
CVE-2026-48931 — nodejs: Node.js HTTP Agent: Information disclosure due to premature response acceptance
CVE-2026-48933 — nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt()
CVE-2026-48934 — nodejs: Node.js: Certification validation bypass in TLS host verification
CVE-2026-48935 — nodejs: Node.js: Unauthorized file metadata modification
CVE-2026-48936 — nodejs: Node.js: Local server can be started without network permission via Permission API flaw
CVE-2026-56847 — nodejs: Node.js: Permission Model flaw allows trace logs to bypass filesystem write restrictions
CVE-2026-56848 — nodejs: Node.js: Heap-use-after-free in HTTP/2 handling can lead to denial of service
CVE-2026-56850 — nodejs: Node.js: mTLS client identities can be reused due to HTTPS Agent connection flaw
CVE-2026-58039 — nodejs: Information disclosure due to improper permission enforcement
CVE-2026-58040 — nodejs: HTTPS Agent TLS session reuse skips hostname verification
CVE-2026-58041 — nodejs: Node.js node:sqlite: Unintended data modification due to stale statement iterator
CVE-2026-58042 — nodejs: Node.js: Denial of Service via DNS responses with excessive A records
CVE-2026-58043 — nodejs: Node.js: Unauthorized filesystem access due to Permission Model enforcement flaw
CVE-2026-58044 — nodejs: Node.js: Request smuggling via HTTP client header truncation
CVE-2026-58045 — nodejs: Node.js: Denial of Service vulnerability
CVE-2026-87018 — undici: undici: Denial of Service via TLS renegotiation with mismatched certificate
CVE-2026-102276 — brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns
CVE-2026-102278 — brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns
CVE-2026-105482 — nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character
CVE-2026-105483 — nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames
CVE-2026-106069 — nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames
CVE-2026-109383 — undici: undici: Certificate validation bypass via dropped TLS options in Agent
CVE-2026-109829 — undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching
CVE-2026-109869 — undici: undici: Denial of Service via unhandled stream error on excessive content encodings
🎯 Affected products32
- Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-1:26.12.1-3.el10_3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-1:26.12.1-3.el10_3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-1:26.12.1-3.el10_3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-1:26.12.1-3.el10_3.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-1:26.12.1-3.el10_3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debuginfo-1:26.12.1-3.el10_3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debuginfo-1:26.12.1-3.el10_3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debuginfo-1:26.12.1-3.el10_3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debuginfo-1:26.12.1-3.el10_3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debugsource-1:26.12.1-3.el10_3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debugsource-1:26.12.1-3.el10_3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debugsource-1:26.12.1-3.el10_3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-debugsource-1:26.12.1-3.el10_3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-devel-1:26.12.1-3.el10_3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-devel-1:26.12.1-3.el10_3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-devel-1:26.12.1-3.el10_3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-devel-1:26.12.1-3.el10_3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-docs-1:26.12.1-3.el10_3.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-full-i18n-1:26.12.1-3.el10_3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-full-i18n-1:26.12.1-3.el10_3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-full-i18n-1:26.12.1-3.el10_3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-full-i18n-1:26.12.1-3.el10_3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-libs-1:26.12.1-3.el10_3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-libs-1:26.12.1-3.el10_3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-libs-1:26.12.1-3.el10_3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-libs-1:26.12.1-3.el10_3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-libs-debuginfo-1:26.12.1-3.el10_3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-libs-debuginfo-1:26.12.1-3.el10_3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs26-libs-debuginfo-1:26.12.1-3.el10_3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- +2 more not shown
✅ Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: No workaround is available for applications that rely on the Permission Model to restrict process.report.writeReport() output paths. Users should upgrade to a fixed Node.js release (22.23.0, 24.17.0, or 26.3.1 and later) as they become available downstream. Workaround: Limit outbound HTTP/1.1 from Node.js clients to trusted backend endpoints with egress firewall rules or network segmentation. Avoid keep-alive connection pools to untrusted hosts where operationally feasible. Workaround: Avoid using the trace_events.createTracing().enable() function in environments that rely on the Node.js Permission Model for file system isolation. Be aware that avoiding this function disables dynamic trace log generation, which may impact performance profiling, APM monitoring, and diagnostic workflows. Workaround: Restrict network access to Node.js HTTP/2 listeners to trusted clients only. If HTTP/2 is not required, disable it to remove the vulnerable handler from the attack surface. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To mitigate this issue, avoid enabling the experimental Node.js Permission Model by not using the `--experimental-permission` flag. Additionally, ensure that untrusted Node.js workloads are executed within robust operating system isolation primitives, such as Linux containers or cgroups, to limit potential impact. Workaround: To mitigate this issue, Node.js applications should be designed to explicitly configure unique HTTPS agents for each distinct target host. Alternatively, applications can avoid TLS session caching when making outbound HTTPS requests to varied third-party endpoints using shared client instances. Implementing these application-level changes will prevent the vulnerable behavior of skipping hostname verification. Applications may require a restart to apply these changes. Workaround: Applications using Node.js that leverage the experimental `node:sqlite` SQL tag store feature should avoid using `DatabaseSync#createTagStore()` and `StatementSyncIterator` to prevent unintended data modification. If this feature is not essential, refactoring the application to remove its usage will mitigate the vulnerability. Workaround: If unused, avoid dns.resolveAny() (prefer narrower resolvers such as resolve4 / lookup). Use trusted DNS resolvers and block untrusted DNS paths. Note that replacing dns.resolveAny() with narrower resolvers may break application features that depend on retrieving non-IP records, such as MX or TXT. Workaround: Avoid enabling the Node.js Permission Model by not using the `--permission` flag when starting Node.js applications. This prevents the vulnerable enforcement mechanism from being active. Disabling the Permission Model may remove an intended security layer if your application relies on it for sandboxing. Workaround: To mitigate, do not pass untrusted strings into dns.resolve; reject hostnames that contain embedded NUL bytes before DNS resolution. Limit which components may perform DNS lookups on attacker-influenced names, and restrict network reachability of those services. --- CME Mitigation Guidance (2026-11-02) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to reject hostnames containing embedded NUL bytes before passing them to Node.js DNS resolution APIs or underlying c-ares C strings: upgrade to Node.js 22.23.4, 24.22.1, and 26.12.1 (or the fixed Nodejs/Hi/Nodejs/Nodejs:24/Nodejs/Nodejs:22/Nodejs/Nodejs:26/Nodejs/Cloudservices/Subscription Central Automation builds), which validate resolve inputs and reject hostnames containing null bytes before passing them to c-ares, closing all 2 injection vectors (embedded NUL byte hostname truncation, domain allowlist validation bypass). Until patched, this is a concern on Applications running Node.js that resolve untrusted, attacker-influenced hostnames via dns.resolve or dns.reverse APIs, so Reject hostnames containing embedded NUL characters before calling dns.resolve or dns.reverse, and restrict which components perform DNS lookups on untrusted input. As a compensating measure, Enforce outbound network egress filtering to restrict unauthorized application connections if a truncated hostname resolves to external destinations and Implement certificate pinning to prevent establishing TLS sessions when connecting to unintended hosts that do not match expected pinned certificates. These controls limit blast radius and contain exploitation, but they do not fix the underlying embedded NUL byte hostname truncation defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high) Workaround: To mitigate do not pass untrusted hostnames that may contain non-ASCII or fullwidth digits into TLS clients such as tls.connect, https.request, or fetch. Restrict outbound TLS connections to trusted destinations only, and segment services that initiate TLS client connections from untrusted networks. --- CME Mitigation Guidance (2026-11-02) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to normalize hostnames and IP representations to standard ASCII before passing destination strings to TLS client calls such as tls.connect, https.request, or fetch: upgrade to Node.js v24.22.1, v26.12.1 (or the fixed Nodejs/Nodejs:24/Nodejs/Nodejs:26/Nodejs/Cloudservices/Subscription Central Automation builds), which fix IP normalization regression in TLS hostname validation to ensure fullwidth digit hostnames are recognized as IP addresses, closing all 2 injection vectors (fullwidth Unicode digit IPv4 connection strings, DNS SAN matching on numeric hostnames). Until patched, this is only a concern on Node.js applications running on 24.x and 26.x runtimes establishing TLS client connections — Node.js 22.x deployments are unaffected — so Do not pass untrusted hostnames or URLs that may contain non-ASCII or fullwidth digits into TLS clients, and restrict outbound TLS connections to trusted destinations. As a compensating measure, Restrict outbound requests to a validated destination allowlist to prevent arbitrary attacker-controlled host strings from reaching Node.js TLS clients and Segment services initiating TLS client connections from untrusted networks to prevent attackers from intercepting or impersonating connections. These controls limit blast radius and contain exploitation, but they do not fix the underlying TLS IP hostname normalization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high) Workaround: To mitigate, reject non-canonical numeric hostnames before opening TLS connections. Restrict outbound TLS to trusted destinations onl…
🔗 References (34)
- selfhttps://access.redhat.com/errata/RHSA-2026:98619
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2490521
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2491494
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493325
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493326
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493329
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493331
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493332
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493333
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493335
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493336
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2493337
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2508485
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2509171
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2509175
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2509178
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2509179
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2509653
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2510853
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2510854
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2510857
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2510858
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2511089
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2542700
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2542707
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553656
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553677
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553678
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2553679
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2559870
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2559873
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2559875
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_98619.json