RHSA-2026:26994HighCVSS 7.5

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

Published
June 18, 2026
Last Modified
August 23, 2026

🔗 CVE IDs covered (6)

CVE-2026-45491 →CVE-2026-45591 →CVE-2026-45736 →CVE-2026-59724 →CVE-2026-59868 →CVE-2026-59870 →

📋 Description

CVE-2026-45491 — dotnet: .NET: Local file tampering via link following vulnerability CVE-2026-45591 — dotnet: ASP.NET Core: Denial of Service via uncontrolled resource consumption CVE-2026-45736 — ws: ws: Uninitialized memory disclosure via websocket.close() with TypedArray CVE-2026-59724 — engine.io: Engine.IO: Denial of Service via crafted WebTransport session ID CVE-2026-59868 — js-yaml: js-yaml: Denial of Service via quadratic CPU time parsing with merge keys CVE-2026-59870 — js-yaml: js-yaml: Denial of Service via crafted YAML ordered-map document

🎯 Affected products4

  • Red Hat Hardened Images
  • dotnet8-0-main@aarch64 as a component of Red Hat Hardened Images
  • dotnet8-0-main@src as a component of Red Hat Hardened Images
  • dotnet8-0-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: Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when they become available. Workaround: Upgrade to js-yaml 5.2.0 or later. Where an immediate upgrade is not possible, avoid parsing untrusted YAML documents that use merge keys ('<<'), or apply size and time limits when parsing untrusted YAML input. Workaround: Avoid using the YAML11_SCHEMA when parsing untrusted YAML input, or upgrade to js-yaml 5.2.1 or later. Applications using the default schema (CORE_SCHEMA) are not affected.

🔗 References (10)