RHSA-2026:38236HighCVSS 7.5

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Published
July 11, 2026
Last Modified
September 10, 2026

🔗 CVE IDs covered (10)

CVE-2026-11525 →CVE-2026-12151 →CVE-2026-53550 →CVE-2026-5078 →CVE-2026-6734 →CVE-2026-59869 →CVE-2026-6733 →CVE-2026-9678 →CVE-2026-9679 →CVE-2026-9697 →

📋 Description

CVE-2026-5078 — morgan: morgan: Log forgery due to unneutralized control characters 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-9679 — undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding 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-53550 — js-yaml: js-yaml: Denial of Service via crafted YAML merge keys CVE-2026-59869 — js-yaml: js-yaml: Denial of Service via crafted YAML documents

🎯 Affected products5

  • Red Hat Hardened Images
  • nodejs24-main@aarch64 as a component of Red Hat Hardened Images
  • nodejs24-main@noarch as a component of Red Hat Hardened Images
  • nodejs24-main@src as a component of Red Hat Hardened Images
  • nodejs24-main@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: 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: 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: To reduce exposure, restrict the processing of untrusted YAML documents by applications that rely on `js-yaml`. Implement robust input validation and sanitization for all YAML data originating from external or untrusted sources. Consider limiting network access to services that parse YAML content to trusted networks or clients through appropriate firewall configurations.

🔗 References (14)