RHSA-2026:54517HighCVSS 7.5

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

Published
August 13, 2026
Last Modified
September 9, 2026

🔗 CVE IDs covered (9)

CVE-2026-45819 →CVE-2026-65904 →CVE-2026-65911 →CVE-2026-65914 →CVE-2026-73089 →CVE-2026-16221 →CVE-2026-65912 →CVE-2026-65913 →CVE-2026-73088 →

📋 Description

CVE-2026-16221 — fast-uri: Fast-uri: Security policy bypass due to URL parsing inconsistency CVE-2026-45819 — baseline-browser-mapping: baseline-browser-mapping: Denial of Service via improper input handling CVE-2026-65904 — DOMPurify: DOMPurify: Cross-Site Scripting via unsanitized DOM elements from different realms CVE-2026-65911 — DOMPurify: DOMPurify: Cross-site scripting due to state leakage in sanitization. CVE-2026-65912 — dompurify: DOMPurify: URI validation bypass leads to cross-site scripting CVE-2026-65913 — dompurify: DOMPurify: Cross-Site Scripting (XSS) via prototype pollution in USE_PROFILES mode CVE-2026-65914 — dompurify: DOMPurify: Cross-Site Scripting vulnerability allows arbitrary code execution CVE-2026-73088 — browserslist: Browserslist: Prototype pollution leading to denial of service CVE-2026-73089 — browserslist: Browserslist: Denial of Service via unbounded memory growth from distinct query results

🎯 Affected products4

  • Red Hat Hardened Images
  • grafana13-1-main@aarch64 as a component of Red Hat Hardened Images
  • grafana13-1-main@src as a component of Red Hat Hardened Images
  • grafana13-1-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: To mitigate this issue, applications utilizing DOMPurify should avoid reusing the same DOMPurify instance when dynamically switching between function and array predicates for ADD_ATTR or ADD_TAGS. Instead, a new DOMPurify instance should be initialized whenever the type of these predicates changes to ensure proper state reset. Workaround: To reduce exposure, ensure that the `browserslist` tool processes only trusted `browserslist-stats.json`, `opts.stats`, and CLI `--stats` data. Avoid using the tool with untrusted input sources in development or build environments. If `browserslist` is integrated into automated pipelines, validate all input data originates from trusted sources.

🔗 References (13)