dbcve.org
GrafanaApplication

CVE-2026-27876

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 11.6.0 / 12.0.0 or later.
See remediation →
97/100
Remediation priority · Urgent
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 chained attack via SQL Expressions and a Grafana Enterprise plugin can lead to a remote arbitrary code execution impact (RCE). This is enabled by a feature in Grafana (OSS), so all users are always recommended to update to avoid future attack vectors going this path. Only instances with the sqlExpressions feature toggle enabled are vulnerable. Only instances in the following version ranges are affected: - 11.6.0 (inclusive) to 11.6.14 (exclusive): 11.6.14 has the fix. 11.5 and below are not affected. - 12.0.0 (inclusive) to 12.1.10 (exclusive): 12.1.10 has the fix. 12.0 did not receive an update, as it is end-of-life. - 12.2.0 (inclusive) to 12.2.8 (exclusive): 12.2.8 has the fix. - 12.3.0 (inclusive) to 12.3.6 (exclusive): 12.3.6 has the fix. - 12.4.0 (inclusive) to 12.4.2 (exclusive): 12.4.2 has the fix. 13.0.0 and above also have the fix: no v13 release is affected.

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

A chained attack combining the SQL Expressions feature (sqlExpressions toggle) in Grafana OSS with a Grafana Enterprise plugin enables remote arbitrary code execution (RCE). The vulnerability is present only when the sqlExpressions feature flag is enabled and affects specific version ranges across Grafana 11.6.x through 12.4.x.

MitigationDisable the sqlExpressions feature toggle if not required, and upgrade to the fixed versions: 11.6.14+, 12.1.10+, 12.2.8+, 12.3.6+, 12.4.2+, or 13.0.0+.

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.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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 installed Grafana version
    Check via Grafana UI (Help → About), run 'grafana-server -v' or 'grafana-cli --version', or query the health API at GET /api/health
    Affected if The installed version falls into any of the affected ranges: < 11.6.0, 11.6.14-12.0.0, 12.1.10-12.2.0, 12.2.8-12.3.0, or 12.3.6-12.4.0
  2. Locate Grafana configuration file
    Common locations are /etc/grafana/grafana.ini, /usr/local/etc/grafana/grafana.ini, or check for custom paths via environment variable GF_CONFIG_PATH
    Affected if Configuration file cannot be located for the next step
  3. Check if sqlExpressions feature is enabled
    Inspect the grafana.ini file under [feature_toggles] section and look for 'enable = sqlExpressions' or check environment variable 'GF_FEATURE_TOGGLES_ENABLE=sqlExpressions'
    Affected if sqlExpressions is explicitly listed as enabled in the configuration or environment variables
  4. Check Grafana edition (Enterprise vs OSS)
    Inspect the same grafana.ini file under [paths] section for 'plugins' directory, or check for enterprise license file at /var/lib/grafana/grafana.license or via UI at Administration → Stats
    Affected if Running Grafana Enterprise with external plugins installed alongside the vulnerable OSS sqlExpressions feature

Environment is affected if running a vulnerable Grafana version AND the sqlExpressions feature toggle is enabled, with the attack surface maximized when using Grafana Enterprise with external plugins.

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.0 / 12.0.0 / 12.2.0 or later
Fixed in 11.6.012.0.012.2.0
Interim mitigation

Disable the sqlExpressions feature toggle if not required, and upgrade to the fixed versions: 11.6.14+, 12.1.10+, 12.2.8+, 12.3.6+, 12.4.2+, or 13.0.0+.

Recommended fix High confidence

Upgrade to Grafana 12.4.2 or later (or the latest stable release). Fixed versions are: 11.6.14, 12.1.10, 12.2.8, 12.3.6, 12.4.2

  1. 1. Identify your current Grafana version by checking the Grafana UI (Settings > About) or running `grafana-server --version`
  2. 2. Identify if the sqlExpressions feature toggle is enabled in your configuration (check grafana.ini or environment variables for `featureToggles.sqlExpressions = true` or similar)
  3. 3. If sqlExpressions is not explicitly needed, disable it as a defense-in-depth measure while planning the upgrade
  4. 4. For Grafana 11.6.x: Upgrade to version 11.6.14 or later (11.6.14 contains the fix)
  5. 5. For Grafana 12.0.x: Note that 12.0 is end-of-life; upgrade to 12.1.10 or later (12.1.10 contains the fix)
  6. 6. For Grafana 12.1.x: Upgrade to version 12.1.10 or later
  7. 7. For Grafana 12.2.x: Upgrade to version 12.2.8 or later
  8. 8. For Grafana 12.3.x: Upgrade to version 12.3.6 or later
Caveat Review Grafana upgrade notes for breaking changes between your current version and target version; major version jumps (e.g., 11.x to 12.x) may have significant changes

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

Fix this in Grafana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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