RHSA-2026:54438HighCVSS 7.4

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Published
August 12, 2026
Last Modified
October 22, 2026

🔗 CVE IDs covered (9)

CVE-2026-85008 →CVE-2026-85014 →CVE-2026-85152 →CVE-2026-84947 →CVE-2026-84961 →CVE-2026-18149 →CVE-2026-48932 →CVE-2026-84890 →CVE-2026-84933 →

📋 Description

CVE-2026-18149 — undici: undici: Denial of Service due to orphaned response body in retry handler CVE-2026-48932 — nodejs: Node.js HTTP client: Request desynchronization due to omitted headers CVE-2026-84890 — undici: undici: Denial of Service via unbounded decompression of compressed responses CVE-2026-84933 — undici: undici: Cross-user cookie disclosure via Set-Cookie caching CVE-2026-84947 — undici: Undici: Response truncation and connection termination CVE-2026-84961 — undici: undici: TLS certificate validation bypass in BalancedPool via dropped connect options CVE-2026-85008 — undici: undici: Integrity failure due to caching of unsafe HTTP method responses CVE-2026-85014 — undici: undici: Denial of Service via WebSocketStream unclean close CVE-2026-85152 — undici: undici: Authentication bypass via cross-origin cache poisoning due to missing origin isolation

🎯 Affected products20

  • Red Hat Hardened Images
  • nodejs24-1:24.18.1-0.2.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • nodejs24-1:24.18.1-0.2.2.hum1@src as a component of Red Hat Hardened Images
  • nodejs24-1:24.18.1-0.2.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • nodejs24-bin-1:24.18.1-0.2.2.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
  • nodejs24-bin-1:24.18.1-0.2.2.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
  • nodejs24-devel-1:24.18.1-0.2.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • nodejs24-devel-1:24.18.1-0.2.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • nodejs24-docs-1:24.18.1-0.2.2.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
  • nodejs24-docs-1:24.18.1-0.2.2.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
  • nodejs24-full-i18n-1:24.18.1-0.2.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • nodejs24-full-i18n-1:24.18.1-0.2.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • nodejs24-libs-1:24.18.1-0.2.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • nodejs24-libs-1:24.18.1-0.2.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • nodejs24-npm-1:11.16.0-1.24.18.1.0.2.2.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
  • nodejs24-npm-1:11.16.0-1.24.18.1.0.2.2.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
  • nodejs24-npm-bin-1:24.18.1-0.2.2.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
  • nodejs24-npm-bin-1:24.18.1-0.2.2.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
  • v8-13.6-devel-3:13.6.233.17-1.24.18.1.0.2.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • v8-13.6-devel-3:13.6.233.17-1.24.18.1.0.2.2.hum1@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: Applications utilizing undici should implement an independent request deadline and ensure the response body is explicitly destroyed upon expiration. The bodyTimeout mechanism alone is insufficient to prevent resource exhaustion in this scenario. 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: Upgrade to undici 7.29.1 or 8.10.2 (or later), where the shared cache interceptor no longer stores or re-serves responses containing Set-Cookie. Where an immediate upgrade is not possible: use a private cache (type: 'private') for per-user responses instead of the shared cache; avoid caching responses that carry a Set-Cookie header; or, if your service itself acts as a shared cache in front of an untrusted origin, strip Set-Cookie from upstream responses before caching them. Workaround: Applications that do not use BalancedPool, or that use it without a custom function-valued connect/tls option, are not affected and require no action. As a workaround until packages are updated, avoid using BalancedPool for any connection that relies on custom TLS certificate validation (e.g. certificate pinning); use Client, Pool, or Agent instead, which are unaffected. The permanent fix is upgrading undici to 7.29.1 or later (7.x line) or 8.10.2 or later (8.x line). Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible to undici 8.10.2 or later.

🔗 References (13)