dbcve.org
GrafanaApplication

CVE-2026-28379

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
A race condition in Grafana Live allows authenticated users with Viewer role to trigger a server crash by sending concurrent requests that cause a fatal map access error. This results in complete service unavailability requiring restart of the Grafana server.

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

A race condition in Grafana Live allows authenticated users with Viewer role to crash the server by sending concurrent requests that cause a fatal map access error, resulting in complete service unavailability requiring Grafana server restart.

MitigationApply the vendor-provided patch or upgrade to a Grafana version that addresses this race condition vulnerability in the Live feature.

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.5.0, < 11.6.14>= 12.2.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. Check Grafana server version
    Run 'grafana-server -v' or check the version from the Grafana admin UI at Server Admin > Stats, or inspect the binary/容器镜像 version
    Affected if The installed version falls within the affected ranges: >= 8.5.0 and < 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 exactly versions 11.6.14, 12.2.8, 12.3.6, 12.4.3, 13.0.0, or 13.0.1
  2. Confirm Grafana Live feature is in use
    Check if the Live streaming feature is enabled by reviewing Grafana configuration files (grafana.ini) for 'live' settings, or check the admin UI under Settings > Live, or look for active WebSocket connections to /api/live endpoints
    Affected if The Live feature is enabled and accessible to authenticated users
  3. Verify Viewer role assignments
    Review user permissions in Grafana by checking Organization > Users with Viewer role, or inspect authentication logs for Viewer role login events
    Affected if There are authenticated users assigned the Viewer role who can access Grafana
  4. Check for crash indicators
    Review Grafana server logs for fatal errors containing 'fatal: concurrent map read and map write' or service restart events coinciding with concurrent /api/live requests from Viewer accounts
    Affected if Server logs show fatal map access errors or unexplained restarts triggered by concurrent Live feature requests

You are affected if your Grafana version is in the affected list AND the Live feature is enabled AND Viewer-role users can send concurrent requests to the Live 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.

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

Apply the vendor-provided patch or upgrade to a Grafana version that addresses this race condition vulnerability in the Live feature.

Recommended fix High confidence

12.4.3 (or 11.6.14/12.2.8/12.3.6 depending on your major version branch)

  1. 1. Identify the currently installed Grafana version using `grafana-server --version` or checking the Grafana configuration
  2. 2. Based on your current major version, plan the upgrade to the minimum fixed release: for Grafana 11.x upgrade to 11.6.14, for 12.2.x upgrade to 12.2.8, for 12.3.x upgrade to 12.3.6, or for 12.4.x upgrade to 12.4.3
  3. 3. Back up your Grafana configuration files (usually in /etc/grafana) and any custom dashboards/plugins
  4. 4. Stop the Grafana service using `systemctl stop grafana-server` or `service grafana-server stop`
  5. 5. Install the appropriate fixed version using your package manager (e.g., apt, yum) or by downloading from grafana.com
  6. 6. Start the Grafana service using `systemctl start grafana-server` or `service grafana-server start`
  7. 7. Verify the upgrade by checking `grafana-server --version` shows the fixed version
  8. 8. Confirm Grafana is operational and the Live feature is functioning without crashes

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

Fix this in Grafana Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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