Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
🔗 CVE IDs covered (21)
📋 Description
CVE-2026-116592 — undici: undici: Cache poisoning via intermediate redirect hops CVE-2026-116630 — undici: undici: Information disclosure via cross-origin redirect cache revalidation CVE-2026-120222 — undici: undici: Denial of Service via uncaught exception during cached response replay CVE-2026-120415 — undici: undici: Information disclosure via unstripped headers during cross-origin redirects CVE-2026-120423 — undici: undici: Subresource Integrity check bypass via improper whitespace parsing CVE-2026-120474 — undici: undici: Information disclosure via shared cache and same-origin redirects CVE-2026-123828 — nodejs: nodejs: Denial of Service via HTTP/2 Alt-Svc heap buffer overflow CVE-2026-123829 — nodejs: Node.js: Information disclosure via improper permission checks in recursive file watching CVE-2026-123862 — nodejs: Node.js: Denial of service via abrupt disconnection during zlib compression CVE-2026-123863 — nodejs: Node.js: Denial of Service via improper HTTP/2 session teardown CVE-2026-123864 — nodejs: nodejs: Information disclosure via HTTPS parser re-entrancy CVE-2026-123865 — nodejs: Node.js: Denial of service via HTTP/2 session resource leak during shutdown CVE-2026-123866 — nodejs: Node.js: Information disclosure via use-after-free during HTTP/2 stream teardown CVE-2026-123867 — nodejs: Node.js: Mutual TLS authorization bypass via incomplete SNI context configuration CVE-2026-123868 — nodejs: nodejs: Denial of service via HTTP/2 memory exhaustion CVE-2026-123871 — nodejs: Node.js: Information disclosure via invalid proxy configuration error messages CVE-2026-123872 — nodejs: Node.js: Client certificate authentication bypass via TLS renegotiation CVE-2026-123874 — nodejs: nodejs: Denial of Service via HTTP/2 use-after-free CVE-2026-123875 — nodejs: nodejs: Denial of Service via cancelled HTTP/2 file downloads CVE-2026-123877 — nodejs: nodejs: Certificate validation bypass via TLS session cache reuse CVE-2026-126051 — nodejs: nodejs: Denial of service via premature socket closure during TLS handshake
🎯 Affected products29
- Red Hat Hardened Images
- nodejs26-1:26.13.1-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs26-1:26.13.1-0.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs26-1:26.13.1-0.1.hum1@src as a component of Red Hat Hardened Images
- nodejs26-1:26.13.1-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs26-bin-1:26.13.1-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs26-bin-1:26.13.1-0.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs26-bin-1:26.13.1-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs26-devel-1:26.13.1-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs26-devel-1:26.13.1-0.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs26-devel-1:26.13.1-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs26-docs-1:26.13.1-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs26-docs-1:26.13.1-0.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs26-docs-1:26.13.1-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs26-full-i18n-1:26.13.1-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs26-full-i18n-1:26.13.1-0.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs26-full-i18n-1:26.13.1-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs26-libs-1:26.13.1-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs26-libs-1:26.13.1-0.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs26-libs-1:26.13.1-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs26-npm-1:11.20.0-1.26.13.1.0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs26-npm-1:11.20.0-1.26.13.1.0.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs26-npm-1:11.20.0-1.26.13.1.0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs26-npm-bin-1:26.13.1-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs26-npm-bin-1:26.13.1-0.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs26-npm-bin-1:26.13.1-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- v8-14.6-devel-3:14.6.202.34-1.26.13.1.0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- v8-14.6-devel-3:14.6.202.34-1.26.13.1.0.1.hum1@s390x as a component of Red Hat Hardened Images
- v8-14.6-devel-3:14.6.202.34-1.26.13.1.0.1.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: Configure Node.js applications utilizing undici to avoid vulnerable interceptor ordering: 1. Reorder interceptors: Structure the interceptor pipeline so caching is evaluated prior to redirection, such as using compose(cache(), redirect()). 2. Isolate cache boundaries: Replace shared originless Agent configurations with origin-bound Client or Pool dispatchers and separate cache stores. 3. Restrict shared caching: Disable shared caching on client requests that permit automated redirect following. Caveats: Disabling shared caching or modifying dispatcher architecture may increase request latency and backend server load. Warning: Applying these application configuration changes requires restarting the affected Node.js service. --- CME Mitigation Guidance (2026-11-06) --- 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 reconfigure undici interceptors to evaluate caching prior to redirection or isolate dispatchers and cache stores per origin: upgrade to undici 7.30.2, 8.12.4+ (or the corresponding fixed Red Hat builds), which account for intermediate redirect hops and enforce cache validation and header retention across all hops before storing responses under the original request key, closing all 3 injection vectors (intermediate redirect bounce through untrusted origin, dropping intermediate Vary header to expose private cached responses, laundering non-storable intermediate redirects via missing no-cache validation). Until patched, this is a concern on Node.js applications using an originless undici Agent composing redirect and shared cache interceptors, so reorder interceptors to evaluate cache before redirect, use origin-bound dispatchers with isolated cache stores, or disable shared caching on requests that permit redirect following. As a compensating measure, block outbound network connections to unapproved external endpoints to prevent reaching attacker-controlled intermediate redirect targets and restrict server-initiated requests and redirect hops to an explicit allowlist of permitted destinations. These controls limit blast radius and contain exploitation, but they do not fix the underlying intermediate redirect cache poisoning defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-208 Outbound Network Egress Restriction (SSRF Blast Radius Containment) (medium) 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: Format Subresource Integrity (SRI) metadata without surrounding whitespace. Ensure that integrity metadata strings passed to fetch calls contain no leading or trailing ASCII whitespace, such as tabs. When specifying multiple cryptographic digests, separate them strictly with a single space character. Caveats: This workaround requires modifying configuration parameters or application input strings where SRI hashes are defined. Applications consuming external or dynamically generated integrity metadata may still remain susceptible if whitespace is not sanitized prior to evaluation. Workaround: To mitigate this vulnerability without applying software updates, apply one of the following application or operational controls: 1. Reorder interceptors: Configure undici dispatchers to register the cache interceptor prior to the redirect interceptor (for example, `compose(cache(), redirect())`). 2. Use isolated dispatchers: Replace originless agents with per-origin Client or Pool dispatchers, or disable shared cache stores (`type: 'shared'`) on requests that transmit credentials. 3. Enforce upstream cache headers: Configure backend web servers or reverse proxies to include `Cache-Control: private`, `Cache-Control: no-store`, or explicit `Vary` headers on user-specific responses. Caveats: Reordering interceptors or disabling shared caching prevents caching of redirected responses, which may increase network traffic and latency to upstream origin services. Warning: Applying dispatcher or application configuration adjustments requires restarting the affected Node.js service for changes to take effect. Workaround: Do not pass attacker-controlled values such as the request :authority into Http2Session.altsvc(). If Alt-Svc is unused, terminate HTTP/2 at a reverse proxy and avoid calling altsvc() with untrusted input. Workaround: On Linux this issue does not apply. On macOS/Windows under --permission, avoid recursive fs.watch() on directories with narrower descendant read grants, or intentionally broaden the read grant to cover watched descendants. Workaround: Avoid calling zlib.params() while streaming compressed output to a remote peer. Prefer fixed compression settings for long-lived streams, and handle peer disconnects without destroying a zlib stream that still has a pending params() flush. Workaround: Terminate HTTP/2 at a trusted reverse proxy and proxy HTTP/1.1 to Node.js (see CME-202). Restrict direct Node.js HTTP/2 listeners to trusted networks only. Workaround: Offload TLS termination to a trusted reverse proxy or load balancer and serve cleartext HTTP from Node.js on localhost only. Restrict direct HTTPS exposure to untrusted clients. Workaround: Terminate HTTP/2 at an upstream reverse proxy and forward HTTP/1.1 to the Node.js backend. Apply connection/rate limits to contain resource exhaustion (see CME-114). Workaround: Terminate HTTP/2 at a reverse proxy and avoid exposing Node.js HTTP/2 directly to untrusted peers. Restrict HTTP/2 endpoints to trusted networks (see CME-202). Workaround: When using server.addContext() for per-host client CAs, always include a server certificate in that SNI context so the host-specific CA is applied. Prefer terminating mTLS at a reverse proxy when possible. Workaround: Terminate HTTP/2 at a reverse proxy and limit request body size and concurrent streams (see CME-114). Restrict Node.js HTTP/2 listeners to trusted networks (see CME-202). Workaround: Avoid placing proxy credentials in the environment of long-lived services; prefer credential helpers or secret stores. Restrict access to logs that may capture ERR_PROXY_INVALID_CONFIG messages. Workaround: Enforce TLS 1.3 to eliminate renegotiation, or terminate TLS at a proxy that does not forward TLS 1.2 renegotiation. Avoid differing per-SNI mTLS policies on one listener when TLS 1.2 remains enabled. Workaround: Avoid stream.respondWithFile()/respondWithFD() for untrusted HTTP/2 clients; serve files over HTTP/1.1 or via a reverse proxy. Restrict HTTP/2 file-serving endpoints to trusted networks (see CME-202). Workaround: Avoid respondWithFile()/respondWithFD() over HTTP/2 for untrusted clients; use HTTP/1.1 or reverse-proxy file serving instead. Restrict HTTP/2 file endpoints to trusted networks (see CME-202). Workaround: Do not reuse a single https.Agent across requests that use different ca trust policies. Create separate Agents per CA policy, or disable TLS session reuse between divergent policies. Workaround: Prefer terminating TLS at a reverse proxy rather than in-process Node.js TLS. If SNICallback, OCSPRequest, newSession/resumeSession, or addContext hooks are unused, avoid configuring them on internet-facing TLS servers.
🔗 References (25)
- selfhttps://access.redhat.com/errata/RHSA-2026:99436
- externalhttps://images.redhat.com/
- externalhttps://access.redhat.com/security/cve/CVE-2026-123872
- externalhttps://access.redhat.com/security/updates/classification/
- externalhttps://access.redhat.com/security/cve/CVE-2026-126051
- externalhttps://access.redhat.com/security/cve/CVE-2026-123877
- externalhttps://access.redhat.com/security/cve/CVE-2026-123874
- externalhttps://access.redhat.com/security/cve/CVE-2026-123868
- externalhttps://access.redhat.com/security/cve/CVE-2026-123864
- externalhttps://access.redhat.com/security/cve/CVE-2026-123875
- externalhttps://access.redhat.com/security/cve/CVE-2026-123866
- externalhttps://access.redhat.com/security/cve/CVE-2026-123863
- externalhttps://access.redhat.com/security/cve/CVE-2026-123871
- externalhttps://access.redhat.com/security/cve/CVE-2026-123867
- externalhttps://access.redhat.com/security/cve/CVE-2026-123865
- externalhttps://access.redhat.com/security/cve/CVE-2026-123829
- externalhttps://access.redhat.com/security/cve/CVE-2026-123862
- externalhttps://access.redhat.com/security/cve/CVE-2026-123828
- externalhttps://access.redhat.com/security/cve/CVE-2026-116630
- externalhttps://access.redhat.com/security/cve/CVE-2026-120222
- externalhttps://access.redhat.com/security/cve/CVE-2026-120423
- externalhttps://access.redhat.com/security/cve/CVE-2026-120474
- externalhttps://access.redhat.com/security/cve/CVE-2026-120415
- externalhttps://access.redhat.com/security/cve/CVE-2026-116592
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_99436.json