RHSA-2026:54178MediumCVSS 7.4

Red Hat Security Advisory: grafana security, bug fix, and enhancement update

Published
August 12, 2026
Last Modified
August 19, 2026

🔗 CVE IDs covered (4)

📋 Description

CVE-2026-8609 — grafana: Grafana: Denial of Service via unbounded memory growth in OAuth login route CVE-2026-33376 — grafana: Grafana Auth Proxy: Unauthorized access due to incorrect IPv6 allow-list default CVE-2026-33377 — grafana: Grafana: Privilege escalation via dashboard overwrite CVE-2026-33382 — grafana: Grafana: Denial of Service via excessive memory allocation from large API request payloads

🎯 Affected products18

  • Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-0:10.2.6-28.el10_2.4.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-0:10.2.6-28.el10_2.4.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-0:10.2.6-28.el10_2.4.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-0:10.2.6-28.el10_2.4.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-0:10.2.6-28.el10_2.4.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debuginfo-0:10.2.6-28.el10_2.4.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debuginfo-0:10.2.6-28.el10_2.4.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debuginfo-0:10.2.6-28.el10_2.4.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debuginfo-0:10.2.6-28.el10_2.4.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debugsource-0:10.2.6-28.el10_2.4.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debugsource-0:10.2.6-28.el10_2.4.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debugsource-0:10.2.6-28.el10_2.4.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-debugsource-0:10.2.6-28.el10_2.4.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-selinux-0:10.2.6-28.el10_2.4.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-selinux-0:10.2.6-28.el10_2.4.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-selinux-0:10.2.6-28.el10_2.4.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • grafana-selinux-0:10.2.6-28.el10_2.4.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: To mitigate this issue, restrict network access to the Grafana instance to trusted internal networks or localhost. If a reverse proxy or load balancer is deployed in front of Grafana, configure it to implement rate limiting on requests to the OAuth login endpoint to prevent an attacker from exhausting system resources. If OAuth is not required, consider disabling it in the Grafana configuration, though this may impact user authentication workflows. Workaround: To mitigate this issue, explicitly specify the intended IPv6 address mask—typically /128 for a single host—within the Grafana Auth Proxy allow-list configuration. This overrides the incorrect default /32 mask, ensuring that network access restrictions are applied strictly as intended. For RHEL: Update the whitelist directive under the [auth.proxy] section in /etc/grafana/grafana.ini. For example, if ::1 is the desired address, configure it explicitly as ::1/128. A restart of the Grafana service (systemctl restart grafana-server) is required for the changes to take effect. Workaround: Audit dashboard-level permissions to ensure that write access is granted only to users who should be able to modify each specific dashboard. Revoke per-dashboard write permissions from Editor users who do not strictly require them. Workaround: Deploy a reverse proxy or API gateway (e.g., Nginx) in front of Grafana configured to strictly limit the maximum HTTP request body size, dropping oversized payloads before they reach the backend. As a defense-in-depth measure, restrict network access to trusted internal clients via firewall rules. Note: Applying these proxy and network changes may require a service reload, causing a temporary interruption.

🔗 References (8)