RHSA-2026:35841HighCVSS 8.1

Red Hat Security Advisory: nodejs24 security, bug fix, and enhancement update

Published
July 6, 2026
Last Modified
August 19, 2026

🔗 CVE IDs covered (15)

CVE-2026-9697 →CVE-2026-42338 →CVE-2026-48615 →CVE-2026-48619 →CVE-2026-6733 →CVE-2026-6734 →CVE-2026-9678 →CVE-2026-48934 →CVE-2026-11525 →CVE-2026-12151 →CVE-2026-48618 →CVE-2026-48928 →CVE-2026-48930 →CVE-2026-48933 →CVE-2026-48935 →

📋 Description

CVE-2026-6733 — undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. CVE-2026-6734 — undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing CVE-2026-9678 — undici: Undici: Information disclosure due to improper cache-control header parsing CVE-2026-9697 — undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy CVE-2026-11525 — undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header CVE-2026-12151 — undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames CVE-2026-42338 — ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input CVE-2026-48615 — nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling 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-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

🎯 Affected products32

  • Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-1:24.18.0-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-1:24.18.0-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-1:24.18.0-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-1:24.18.0-1.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-1:24.18.0-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debuginfo-1:24.18.0-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debuginfo-1:24.18.0-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debuginfo-1:24.18.0-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debuginfo-1:24.18.0-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debugsource-1:24.18.0-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debugsource-1:24.18.0-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debugsource-1:24.18.0-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-debugsource-1:24.18.0-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-devel-1:24.18.0-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-devel-1:24.18.0-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-devel-1:24.18.0-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-devel-1:24.18.0-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-docs-1:24.18.0-1.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-full-i18n-1:24.18.0-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-full-i18n-1:24.18.0-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-full-i18n-1:24.18.0-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-full-i18n-1:24.18.0-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-libs-1:24.18.0-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-libs-1:24.18.0-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-libs-1:24.18.0-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-libs-1:24.18.0-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-libs-debuginfo-1:24.18.0-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-libs-debuginfo-1:24.18.0-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • nodejs24-libs-debuginfo-1:24.18.0-1.el10_2.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: The single most impactful mitigation is applying network egress controls to restrict which external destinations affected applications can reach. Because the vulnerability causes requests to be misrouted to wrong origins, limiting the set of reachable origins directly reduces the attack surface. These controls collectively limit the blast radius of the connection pool misrouting — the attacker must compromise one of the explicitly allowed destinations rather than any arbitrary origin — but they do not fix the underlying logic bug. 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.

🔗 References (19)