RHSA-2026:35892HighCVSS 8.1

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

Published
July 6, 2026
Last Modified
October 19, 2026

🔗 CVE IDs covered (16)

📋 Description

CVE-2026-6733 — undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. CVE-2026-9678 — undici: Undici: Information disclosure due to improper cache-control header parsing 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-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-48937 — nodejs: Node.js HTTP/2 Server: Denial of Service due to continued data acceptance after GOAWAY frame

🎯 Affected products44

  • Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.src (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debuginfo-1:22.23.1-1.module+el9.8.0+24457+996af7aa.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debuginfo-1:22.23.1-1.module+el9.8.0+24457+996af7aa.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debuginfo-1:22.23.1-1.module+el9.8.0+24457+996af7aa.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debuginfo-1:22.23.1-1.module+el9.8.0+24457+996af7aa.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debugsource-1:22.23.1-1.module+el9.8.0+24457+996af7aa.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debugsource-1:22.23.1-1.module+el9.8.0+24457+996af7aa.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debugsource-1:22.23.1-1.module+el9.8.0+24457+996af7aa.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-debugsource-1:22.23.1-1.module+el9.8.0+24457+996af7aa.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-devel-1:22.23.1-1.module+el9.8.0+24457+996af7aa.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-devel-1:22.23.1-1.module+el9.8.0+24457+996af7aa.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-devel-1:22.23.1-1.module+el9.8.0+24457+996af7aa.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-devel-1:22.23.1-1.module+el9.8.0+24457+996af7aa.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-docs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.noarch (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-full-i18n-1:22.23.1-1.module+el9.8.0+24457+996af7aa.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-full-i18n-1:22.23.1-1.module+el9.8.0+24457+996af7aa.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-full-i18n-1:22.23.1-1.module+el9.8.0+24457+996af7aa.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-full-i18n-1:22.23.1-1.module+el9.8.0+24457+996af7aa.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-libs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-libs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-libs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-libs-1:22.23.1-1.module+el9.8.0+24457+996af7aa.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-libs-debuginfo-1:22.23.1-1.module+el9.8.0+24457+996af7aa.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-libs-debuginfo-1:22.23.1-1.module+el9.8.0+24457+996af7aa.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • nodejs-libs-debuginfo-1:22.23.1-1.module+el9.8.0+24457+996af7aa.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • +14 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: 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: Restrict Node.js HTTP/2 servers to trusted clients with host firewall or network segmentation. If HTTP/2 is not required, disable the HTTP/2 server API.

🔗 References (17)