dbcve.org
GrafanaApplication

CVE-2026-28376

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 11.6.14 / 12.2.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Grafana Live push endpoint can be exploited to cause unbounded memory allocation by sending a large or streaming request body, potentially leading to out-of-memory conditions. An authenticated user with access to the Grafana Live API can trigger this issue.

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 · moderate confidence

The Grafana Live push endpoint lacks proper bounds checking on request body size, allowing authenticated users to send large or streaming data that causes unbounded memory allocation on the server, potentially resulting in out-of-memory conditions.

MitigationImplement request body size limits and proper streaming/chunking controls on the Grafana Live push endpoint to prevent unbounded memory allocation; also consider rate limiting and monitoring for anomalous memory usage patterns.

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:>= 8.0.0, < 11.6.14>= 12.0.0, < 12.2.8>= 12.3.0, < 12.3.6>= 12.4.0, < 12.4.3= 11.6.14= 12.2.8= 12.3.6= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine Grafana version
    Run 'grafana-server -v' or check the version file typically at /usr/share/grafana/VERSION or /var/lib/grafana/current_version. In Docker, use 'docker exec <container> grafana-server -v'. Alternatively, query the Grafana API at GET /api/health
    Affected if The installed version falls within any of the affected ranges: >= 8.0.0 and < 11.6.14; >= 12.0.0 and < 12.2.8; >= 12.3.0 and < 12.3.6; >= 12.4.0 and < 12.4.3; or equals 11.6.14, 12.2.8, 12.3.6, 12.4.3, 13.0.0, or 13.0.1
  2. Verify Grafana Live feature is enabled
    Inspect the Grafana configuration file (grafana.ini or defaults.ini) for the [live] section. Look for 'enabled = true' or check if the feature flag is not explicitly disabled. In Kubernetes, check the ConfigMap or environment variables for 'GF_LIVE_ENABLED'
    Affected if Grafana Live is enabled (the vulnerability only applies when the Live feature is active)
  3. Confirm push endpoint is accessible
    Test connectivity to the Grafana Live push endpoint at /api/live/push/<channel_id> using curl: 'curl -X POST http://<grafana-host>:<port>/api/live/push/test -d "test"'. Check if the endpoint responds (may require authentication)
    Affected if The push endpoint is reachable without proper body size restrictions (this confirms the attack surface exists)

You are affected if your Grafana version is in the affected list, Grafana Live is enabled, and the push endpoint accepts requests without enforced body size limits.

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.

dbcve · scoped
Upgrade available Upgrade to 11.6.14 / 12.2.8 / 12.3.6 or later
Fixed in 11.6.1412.2.812.3.6
Interim mitigation

Implement request body size limits and proper streaming/chunking controls on the Grafana Live push endpoint to prevent unbounded memory allocation; also consider rate limiting and monitoring for anomalous memory usage patterns.

Recommended fix High confidence

Upgrade to Grafana 11.6.14 (for 8.x-11.x), 12.2.8 (for 12.0.x-12.2.x), 12.3.6 (for 12.3.x), or 12.4.3 (for 12.4.x)

  1. 1. Identify the currently running Grafana version using `grafana-cli --version` or checking the Grafana UI at Server > Stats
  2. 2. Determine the appropriate upgrade target based on your current major version: For 8.x-11.x lines, upgrade to 11.6.14 or later; For 12.0.0-12.2.x, upgrade to 12.2.8 or later; For 12.3.x, upgrade to 12.3.6 or later; For 12.4.x, upgrade to 12.4.3 or later
  3. 3. Review the Grafana release notes for the target version to check for any breaking changes or migration requirements
  4. 4. Back up your Grafana configuration, database, and any custom dashboards
  5. 5. Stop the Grafana service
  6. 6. Install the fixed Grafana version using your package manager or by downloading from grafana.com
  7. 7. Verify the service starts successfully and review logs for any errors
  8. 8. Confirm the upgrade by checking the Grafana version in the UI or via CLI
Caveat Review release notes for the target version for potential breaking changes; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28376 — 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-28376 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