dbcve.org
GrafanaApplication

CVE-2026-33378

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
Using the $__timeGroup macro, one can achieve an OOM by overloading the server. This requires a SQL datasource. If the server is set up to auto-restart, the impact is minimal or non-existent, as the attack can take upwards of half an hour to crash the 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

The $__timeGroup macro in Grafana can be abused to cause an out-of-memory (OOM) condition when used with a SQL datasource. By repeatedly invoking this macro, an attacker can gradually exhaust server memory over an extended period (upwards of 30 minutes), leading to server crash.

MitigationConfigure automatic server restart to minimize downtime; additionally, restrict access to SQL datasources and implement rate limiting on macro usage to prevent resource 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:>= 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. Identify Grafana version
    Run 'grafana-server -v' or check the Grafana UI at Server Admin > Stats, or inspect the installed package version
    Affected if The installed version falls within 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. Determine if SQL datasources are in use
    Check Configuration > Data Sources in Grafana UI, or inspect provisioning files in /etc/grafana/provisioning/datasources/
    Affected if Any SQL-based datasource (MySQL, PostgreSQL, MSSQL, Oracle, or SQLite) is configured and accessible to Grafana
  3. Identify usage of $__timeGroup macro in queries
    Review dashboard queries in the Grafana UI, or search query JSON files in /var/lib/grafana/dashboards/ for the string '$__timeGroup'
    Affected if Dashboards contain queries using the $__timeGroup macro with SQL datasources
  4. Monitor for memory exhaustion patterns
    Review Grafana server memory metrics over a 30+ minute period. Check for gradually increasing memory consumption that does not release, especially when dashboards with $__timeGroup queries are accessed repeatedly
    Affected if Memory usage grows steadily without plateauing and approaches system limits during extended query activity

A Grafana instance is affected if it runs a vulnerable version, has SQL datasources configured, and uses the $__timeGroup macro in dashboard queries, making it susceptible to gradual OOM conditions under repeated macro invocation.

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

Configure automatic server restart to minimize downtime; additionally, restrict access to SQL datasources and implement rate limiting on macro usage to prevent resource exhaustion.

Recommended fix High confidence

Upgrade to Grafana 11.6.14 (for 11.x), 12.2.8 (for 12.0-12.2), 12.3.6 (for 12.3), or 12.4.3 (for 12.4+); or migrate to the latest stable 12.x release

  1. 1. Identify the currently installed Grafana version using `grafana-cli --version` or checking the Grafana UI at Server > Stats
Caveat Review Grafana upgrade notes for your version path; may require plugin compatibility checks

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

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-33378 — 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-33378 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