Grafana: Pre-authentication denial of service in the public dashboard query handlerGHSA-3w66-95m3-8jxg
HIGHFix: grafana/grafana#125789GHSA-3w66-95m3-8jxg is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in github.com/grafana/grafana. A fix is available for github.com/grafana/grafana — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3w66-95m3-8jxg.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-3w66-95m3-8jxg by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafanaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
The public dashboard query endpoint does not limit request body size before processing, allowing unauthenticated attackers to trigger excessive memory allocation by sending arbitrarily large JSON payloads. This can lead to denial of service through memory exhaustion. No valid dashboard access token or authentication is required to exploit this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/grafana | ≥ 2.0.0-beta1 | No fix |
| 🐹Go | github.com/grafana/grafana | ≥ 12.0.0 | No fix |
| 🐹Go | github.com/grafana/grafana | ≥ 12.3.0 | No fix |
| 🐹Go | github.com/grafana/grafana | ≥ 12.4.0 | No fix |
| 🐹Go | github.com/grafana/grafana | ≥ 13.0.0 | No fix |
| 🐹Go | github.com/grafana/grafana | all versions | 1.9.2-0.20260616075434-82ef13993059go get github.com/grafana/grafana@v1.9.2-0.20260616075434-82ef13993059 |
Affected Products
grafanagrafanaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of github.com/grafana/grafana has shipped for GHSA-3w66-95m3-8jxg yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This is an Important denial of service vulnerability in Grafana, affecting Red Hat products that include Grafana. Unauthenticated remote attackers can exploit the public dashboard query endpoint by sending large JSON payloads, leading to excessive memory allocation and potential service disruption. The absence of…
Restrict network access to the Grafana instance to only trusted clients and networks. This can be achieved by configuring firewall rules to limit inbound connections to the Grafana service port. If Grafana is exposed via a reverse proxy, ensure the proxy is configured to limit request body sizes to prevent large payloads from reaching Grafana. A service restart may be required for network configuration changes to take effect.Source: Red Hat security advisory for GHSA-3w66-95m3-8jxg (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | grafana-0:10.2.6-28.el10_2.4 | RHSA-2026:54178 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | grafana-0:10.2.6-26.el10_0 | RHSA-2026:67517 |
| Red Hat Enterprise Linux 8 | grafana-0:9.2.10-32.el8_10.1 | RHSA-2026:54243 |
| Red Hat Enterprise Linux 9 | grafana-0:10.2.6-23.el9_8.1 | RHSA-2026:54184 |
| Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions | grafana-0:9.2.10-28.el9_4 | RHSA-2026:76795 |
| Red Hat Enterprise Linux 9.6 Extended Update Support | grafana-0:10.2.6-23.el9_6 | RHSA-2026:67518 |
| Red Hat Advanced Cluster Management for Kubernetes 2.13 | rhacm2/acm-grafana-rhel9:1790177771 | RHSA-2026:72885 |
| Red Hat Hardened Images | grafana13-1-main-13.1.1-0.2.hum1 | RHSA-2026:47618 |
Frequently Asked Questions
Is GHSA-3w66-95m3-8jxg in your dependencies?
Find it across Go, including transitive dependencies.