# CVE-2026-42127: Pre-authentication denial of service in the public dashboard query endpoint > Unauthenticated attackers can cause denial of service in Grafana by sending large JSON payloads to the public dashboard query endpoint, exhausting server memory. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jun 2026 - **Updated:** 27 Aug 2026 - **Also known as:** ALSA-2026:54184, BIT-grafana-2026-42127, CLSA-2026-1783354657, GHSA-3w66-95m3-8jxg, GO-2026-6541, MINI-2mgv-wr45-cxgp, MINI-46jm-83j8-r9p3, MINI-4hm8-36jj-fr7v, MINI-542r-pgw2-3w7x, MINI-5hxf-j6g5-vv7g, MINI-9c8g-7c7v-mrx2, MINI-cppm-35gq-cppq, MINI-j8q8-p6j7-76fw, MINI-jf64-m34g-66rw, MINI-qm3g-5ch8-26rw, MINI-r7mc-jmvg-6qj8, MINI-r9f5-pgv3-gv5p, MINI-vqpw-9q8q-hrvj, MINI-wj4v-2fp8-6pgp, RHSA-2026:54184, RLSA-2026:54184, UBUNTU-CVE-2026-42127 ## What is CVE-2026-42127? CVE-2026-42127 is a high-severity denial of service vulnerability in Grafana Grafana, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-42127? 15 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/grafana/grafana` | Go | All versions | None | | `github.com/grafana/grafana` | Go | All versions | 1.9.2-0.20260616075434-82ef13993059 | | `github.com/grafana/grafana` | Go | All versions | 1.9.2-0.20260616075434-82ef13993059 | | `github.com/grafana/grafana` | Go | From 12.0.0 | None | | `github.com/grafana/grafana` | Go | From 12.0.0 | None | | `github.com/grafana/grafana` | Go | From 12.3.0 | None | | `github.com/grafana/grafana` | Go | From 12.3.0 | None | | `github.com/grafana/grafana` | Go | From 12.4.0 | None | | `github.com/grafana/grafana` | Go | From 12.4.0 | None | | `github.com/grafana/grafana` | Go | From 13.0.0 | None | | `github.com/grafana/grafana` | Go | From 13.0.0 | None | | `github.com/grafana/grafana` | Go | From 2.0.0-beta1 | None | | `github.com/grafana/grafana` | Go | From 2.0.0-beta1 | None | | `github.com/grafana/grafana` | Go | From 2.0.0-beta1+incompatible | None | | `grafana` | Bitnami | All versions | 11.6.15, 12.2.9, 12.3.7, 12.4.4, 12.2.9, 12.3.7, 12.4.4, 13.0.2 | | `grafana` | AlmaLinux:9 | All versions | 10.2.6-23.el9_8.1 | | `grafana-selinux` | AlmaLinux:9 | All versions | 10.2.6-23.el9_8.1 | | `grafana` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.2.6-23.el9_8.1 | | `grafana-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.2.6-23.el9_8.1 | | `grafana-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.2.6-23.el9_8.1 | | `grafana-selinux` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.2.6-23.el9_8.1 | | `grafana` | Rocky Linux:9 | All versions | 0:10.2.6-23.el9_8.1 | Products: Grafana Grafana. ## How do I fix CVE-2026-42127? Upgrade github.com/grafana/grafana to 1.9.2-0.20260616075434-82ef13993059 or later. ## Is CVE-2026-42127 being exploited? There is no known exploitation of CVE-2026-42127 in the wild and no public exploit code. ## Other vulnerabilities in Grafana Grafana - [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild) - [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0) - [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8) - [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8) - [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-42127 and fix it if it is affected. What it is: CVE-2026-42127 is a high-severity denial of service vulnerability in Grafana Grafana, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-42127 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/grafana/grafana (Go): affected all versions; no fix listed - github.com/grafana/grafana (Go): affected all versions; fixed in 1.9.2-0.20260616075434-82ef13993059 - github.com/grafana/grafana (Go): affected all versions; fixed in 1.9.2-0.20260616075434-82ef13993059 - github.com/grafana/grafana (Go): affected from 12.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.3.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.3.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.4.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.4.0; no fix listed - github.com/grafana/grafana (Go): affected from 13.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 13.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 2.0.0-beta1; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-42127/ (Markdown: https://insights.sbomify.com/CVE-2026-42127/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42127 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42127 - OSV: https://osv.dev/vulnerability/CVE-2026-42127 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-42127/ Summaries are generated and may contain mistakes; the official description above is the record.