dbcve.org
GrafanaApplication

CVE-2026-27879

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 8.0.0 / 12.0.0 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 resample query can be used to trigger out-of-memory crashes in Grafana.

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

In Grafana, a specially crafted resample query can trigger excessive memory consumption leading to out-of-memory crashes. The vulnerability stems from insufficient resource limits or memory handling in the resample query processing functionality.

MitigationRestrict or limit the complexity of resample queries in Grafana dashboards and ensure Grafana is updated to the latest patched version once available. Implement query timeout and memory limits where possible.

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.1.10, < 12.2.0>= 12.2.8, < 12.3.0>= 12.3.6, < 12.4.0

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. Identify Grafana version
    Run 'grafana-server --version' or check the version from the admin UI at /api/health or the grafana version file/package
    Affected if The installed version falls within any of these ranges: < 8.0.0; >= 11.6.14 and < 12.0.0; >= 12.1.10 and < 12.2.0; >= 12.2.8 and < 12.3.0; >= 12.3.6 and < 12.4.0
  2. Check for resample query usage
    Search dashboard JSON definitions or query editor configurations for resample operations (common in Prometheus/InfluxDB data sources using the resample function)
    Affected if Resample queries are actively used in any Grafana dashboard or panel
  3. Monitor memory consumption
    Review Grafana logs for out-of-memory errors or check system memory usage during periods of active query execution
    Affected if Grafana experiences OOM crashes or excessive memory growth when resample queries are executed
  4. Check for query timeout configurations
    Inspect grafana.ini for [dataproxy] timeout settings and any query timeout configurations in data source settings
    Affected if No query timeouts or memory limits are configured, allowing unbounded query execution

You are affected if your Grafana version is in the vulnerable ranges AND you use resample queries in your dashboards, as the combination of both enables the memory exhaustion attack vector.

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 8.0.0 / 12.0.0 / 12.2.0 or later
Fixed in 8.0.012.0.012.2.0
Interim mitigation

Restrict or limit the complexity of resample queries in Grafana dashboards and ensure Grafana is updated to the latest patched version once available. Implement query timeout and memory limits where possible.

Recommended fix High confidence

Grafana 12.3.0 (or latest stable)

  1. 1. Check current Grafana version by running `grafana-server -v` or checking the Grafana admin UI status page.
  2. 2. Identify which version branch you are currently on (8.x, 11.x, 12.1.x, or 12.2.x).
  3. 3. For Grafana < 8.0.0: Upgrade to Grafana 8.0.0 or later (preferably the latest 8.x LTS).
  4. 4. For Grafana 11.6.x: Upgrade to Grafana 12.0.0 or later.
  5. 5. For Grafana 12.1.x: Upgrade to Grafana 12.2.0 or later.
  6. 6. For Grafana 12.2.x: Upgrade to Grafana 12.3.0 or later.
  7. 7. After upgrade, restart the Grafana service using `systemctl restart grafana-server` or the equivalent for your deployment.
  8. 8. Verify the upgrade was successful and Grafana is functioning normally.
Caveat Major version upgrades (e.g., 8.x to 11.x/12.x) may introduce breaking changes in dashboard configurations, plugins, and provisioning; review Grafana migration notes

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

Fix this in Grafana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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