dbcve.org
GrafanaApplication

CVE-2026-33380

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 vulnerability in SQL Expressions allows an authenticated attacker to read arbitrary files from the Grafana server's filesystem. Only instances with the sqlExpressions feature toggle enabled are vulnerable.

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 path traversal vulnerability in Grafana's SQL Expressions feature allows authenticated attackers to read arbitrary files from the server's filesystem when the sqlExpressions feature toggle is enabled. This is essentially a local file inclusion (LFI) issue that bypasses intended access controls.

MitigationDisable the sqlExpressions feature toggle if not required in production environments, or ensure strict access controls and apply vendor patches when available.

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.0, < 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Verify if sqlExpressions feature toggle is enabled
    Inspect your Grafana configuration file (grafana.ini) for 'sqlExpressions' under [feature_toggles] section, or check environment variables for GF_FEATURE_TOGGLES_ENABLE containing 'sqlExpressions'. The vulnerability only applies when this feature is explicitly enabled.
    Affected if sqlExpressions is listed as enabled in your configuration or environment variables
  2. Determine installed Grafana version
    Run 'grafana-cli --version' or 'grafana-server -v' from the command line, or query the Grafana HTTP API at /api/health. Alternatively, check your package manager or docker image tag.
    Affected if The installed version falls within any of these ranges: 11.6.0-11.6.13, 12.2.0-12.2.7, 12.3.0-12.3.5, 12.4.0-12.4.2, or 13.0.0
  3. Confirm both conditions are met
    You are affected only if BOTH conditions are true: (1) sqlExpressions feature is enabled AND (2) your installed version matches one of the affected version ranges above.
    Affected if You have both sqlExpressions enabled AND a vulnerable version installed

You are affected only if the sqlExpressions feature toggle is enabled AND your Grafana version falls within one of the vulnerable version ranges.

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

Disable the sqlExpressions feature toggle if not required in production environments, or ensure strict access controls and apply vendor patches when available.

Recommended fix Moderate confidence

Grafana 11.6.14, 12.2.8, 12.3.6, or 12.4.3 (depending on your current major version branch)

  1. 1. Identify your current Grafana version by checking the Grafana UI (Settings > About) or running `grafana-server -v`
  2. 2. Identify if the sqlExpressions feature toggle is enabled in your configuration (check your.ini or custom.ini for `enable_features = sqlExpressions` or similar)
  3. 3. If sqlExpressions is enabled and upgrading immediately is not possible, disable it by removing it from the enable_features setting in your Grafana configuration file
  4. 4. Plan to upgrade to the appropriate fixed version based on your current major version: 11.6.x users should upgrade to 11.6.14, 12.2.x to 12.2.8, 12.3.x to 12.3.6, 12.4.x to 12.4.3
  5. 5. Before upgrading, backup your Grafana database and configuration files
  6. 6. Perform the upgrade following standard Grafana upgrade procedures for your deployment method (package manager, Docker, etc.)
  7. 7. After upgrade, verify Grafana is functioning correctly and the sqlExpressions feature (if needed) works as expected
Caveat Minor version upgrades within the same major version typically have no breaking changes, but always review release notes before upgrading

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

Fix this in Grafana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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