RHSA-2026:66008HighCVSS 7.5

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

Published
September 9, 2026
Last Modified
September 11, 2026

🔗 CVE IDs covered (11)

CVE-2026-84947 →CVE-2026-85014 →CVE-2026-18149 →CVE-2026-28378 →CVE-2026-84890 →CVE-2026-84933 →CVE-2026-84961 →CVE-2026-85008 →CVE-2026-14199 →CVE-2026-18540 →CVE-2026-19534 →

📋 Description

CVE-2026-14199 — grafana: Grafana: Session takeover via Auth Proxy cache key collision CVE-2026-18149 — undici: undici: Denial of Service due to orphaned response body in retry handler CVE-2026-18540 — undici: undici: HTTP response splitting via retry interceptor CVE-2026-19534 — undici: undici: Denial of Service via unrequested WebSocket subprotocol CVE-2026-28378 — grafana: Grafana: Unauthorized public dashboard deletion across organizations CVE-2026-84890 — undici: undici: Denial of Service via unbounded decompression of compressed responses CVE-2026-84933 — undici: undici: Cross-user cookie disclosure via Set-Cookie caching CVE-2026-84947 — undici: Undici: Response truncation and connection termination CVE-2026-84961 — undici: undici: TLS certificate validation bypass in BalancedPool via dropped connect options CVE-2026-85008 — undici: undici: Integrity failure due to caching of unsafe HTTP method responses CVE-2026-85014 — undici: undici: Denial of Service via WebSocketStream unclean close

🎯 Affected products4

  • Red Hat Hardened Images
  • grafana12-4-main@aarch64 as a component of Red Hat Hardened Images
  • grafana12-4-main@src as a component of Red Hat Hardened Images
  • grafana12-4-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: Set [auth.proxy] sync_ttl = 0 to disable the identity cache (identity is then synced on every request), or upgrade to a fixed version: 11.0.0+, 12.4.10+ (12.4.x), 13.0.8+ (13.0.x), 13.1.5+ (13.1.x), or 13.2.1+ (13.2.x and newer — 13.2.0 itself is still vulnerable). Workaround: Applications utilizing undici should implement an independent request deadline and ensure the response body is explicitly destroyed upon expiration. The bodyTimeout mechanism alone is insufficient to prevent resource exhaustion in this scenario. Workaround: Disable interceptors.retry() for untrusted upstreams, or set maxRetries: 0 on the retry interceptor configuration. Alternatively, remove or recalculate the Content-Length header before forwarding a response body assembled by undici to downstream HTTP/1.1 peers. 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: Since this vulnerability only affects the Public Dashboards feature, environments that do not utilize public dashboards can completely neutralize the risk by disabling the feature. This removes the vulnerable endpoint from the attack surface entirely. Workaround: Upgrade to undici 7.29.1 or 8.10.2 (or later), where the shared cache interceptor no longer stores or re-serves responses containing Set-Cookie. Where an immediate upgrade is not possible: use a private cache (type: 'private') for per-user responses instead of the shared cache; avoid caching responses that carry a Set-Cookie header; or, if your service itself acts as a shared cache in front of an untrusted origin, strip Set-Cookie from upstream responses before caching them. Workaround: Applications that do not use BalancedPool, or that use it without a custom function-valued connect/tls option, are not affected and require no action. As a workaround until packages are updated, avoid using BalancedPool for any connection that relies on custom TLS certificate validation (e.g. certificate pinning); use Client, Pool, or Agent instead, which are unaffected. The permanent fix is upgrading undici to 7.29.1 or later (7.x line) or 8.10.2 or later (8.x line).

🔗 References (16)