Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
🔗 CVE IDs covered (10)
📋 Description
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-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-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-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
🎯 Affected products29
- Red Hat Hardened Images
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@src as a component of Red Hat Hardened Images
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- v8-12.4-devel-3:12.4.254.21-1.22.23.5.2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- v8-12.4-devel-3:12.4.254.21-1.22.23.5.2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- v8-12.4-devel-3:12.4.254.21-1.22.23.5.2.3.2.3.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: 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: 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: 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 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.
🔗 References (14)
- selfhttps://access.redhat.com/errata/RHSA-2026:99433
- 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-123877
- 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-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
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_99433.json