dbcve.org
GrafanaApplication

CVE-2026-42127

HIGH · 7.5 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to after 13.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The public dashboard query endpoint lacks request body size validation, allowing unauthenticated attackers to send arbitrarily large JSON payloads that cause excessive memory allocation and eventual denial of service through memory exhaustion.

MitigationImplement request body size limits on the dashboard query endpoint (e.g., using middleware or framework-level size constraints) to reject oversized payloads before parsing, preventing memory exhaustion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:<= 11.6.14>= 12.2.0, <= 12.2.8>= 12.3.0, <= 12.3.6>= 12.4.0, <= 12.4.3>= 13.0.0, <= 13.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana version
    Run 'grafana-server -v' or check the version file (typically /usr/share/grafana/version or via the Grafana web UI at /api/health), or query the API endpoint /api/frontend/settings to retrieve the running version
    Affected if The installed version falls within any of these ranges: <= 11.6.14, >= 12.2.0 and <= 12.2.8, >= 12.3.0 and <= 12.3.6, >= 12.4.0 and <= 12.4.3, or >= 13.0.0 and <= 13.0.1
  2. Confirm public dashboard feature is enabled
    Check Grafana configuration file (grafana.ini) for 'public_dashboards.enabled = true' setting, or query the API endpoint GET /api/dashboards/uid/{uid} with 'publicDashboardAccessToken' to verify public access exists
    Affected if Public dashboards are enabled and accessible without authentication
  3. Verify request body size limits are absent
    Inspect the reverse proxy (nginx, Apache, traefik) configuration in front of Grafana for client_max_body_size or equivalent limits, and check grafana.ini for any [server] body_size_limit or similar settings
    Affected if No body size limit is configured on the Grafana endpoint or reverse proxy, allowing unlimited request body sizes
  4. Locate the dashboard query endpoint
    Review Grafana API documentation or network traffic logs for requests to /api/public/dashboards/{dashboard_uid}/queries or similar public query endpoints
    Affected if The public dashboard query endpoint is accessible and accepts JSON payloads without size restrictions

You are affected if your Grafana version is one of the listed vulnerable versions AND public dashboards are enabled with no request body size limits configured on the query endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 13.0.1
Interim mitigation

Implement request body size limits on the dashboard query endpoint (e.g., using middleware or framework-level size constraints) to reject oversized payloads before parsing, preventing memory exhaustion.

Fix this in Grafana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42127 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data