dbcve.org
SnowflakeApplication · Grafana

CVE-2026-28381

HIGH · 8.1 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to after 1.14.12 or later.
See remediation →
87/100
Remediation priority · High
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
The Snowflake datasource allows for GET/PUT commands, which can allow any user with access to run queries against the data source to read/write files between the local grafana server and the connected Snowflake host.

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 Grafana Snowflake datasource exposes GET/PUT file transfer commands that allow any user with datasource query access to read from or write files to the local Grafana server filesystem through the connected Snowflake host, effectively bypassing proper authorization boundaries.

MitigationRestrict datasource query permissions to trusted users only, and disable or heavily restrict GET/PUT command capabilities in the Snowflake datasource configuration unless explicitly required for legitimate use cases.

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
SnowflakeApplication
Affected:>= 1.14.7, <= 1.14.12

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify Grafana Snowflake datasource plugin installation
    Locate the Snowflake datasource plugin in your Grafana installation. Check the Grafana plugins directory (typically /var/lib/grafana/plugins or %PROGRAMDATA%\Grafana\plugins on Windows), or use 'grafana-cli plugins list' to enumerate installed plugins.
    Affected if The Snowflake datasource plugin is present in the Grafana instance
  2. Determine installed Snowflake plugin version
    Retrieve the version number of the installed Snowflake datasource plugin. This can be found in the plugin's plugin.json file within its directory, or via the Grafana UI under Configuration > Plugins > Snowflake.
    Affected if The installed version falls within >= 1.14.7 and <= 1.14.12
  3. Inspect Snowflake datasource GET/PUT configuration
    Open the Snowflake datasource configuration in Grafana (Configuration > Data Sources > Snowflake). Locate settings related to file transfer commands, often labeled as 'Allow GET/PUT commands' or similar file transfer enablement options.
    Affected if GET or PUT command capabilities are enabled in the datasource configuration
  4. Review datasource query permission scope
    Examine the access control settings for the Snowflake datasource. Check which users or teams have query access permissions to this datasource, typically found in Grafana's permission settings for the datasource.
    Affected if Query permissions are granted to untrusted users or broadly to many users (e.g., All Editors, All Viewers, or large user groups)
  5. Verify filesystem access via query editor
    If you have query access, attempt to test file transfer capabilities through the Snowflake query editor using GET or PUT statements to confirm the feature is functional and exploitable.
    Affected if GET/PUT commands execute successfully against the Grafana server filesystem

You are affected if the Grafana Snowflake datasource plugin version is between 1.14.7 and 1.14.12, GET/PUT file transfer commands are enabled, and untrusted users have datasource query access.

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 a release after 1.14.12
Interim mitigation

Restrict datasource query permissions to trusted users only, and disable or heavily restrict GET/PUT command capabilities in the Snowflake datasource configuration unless explicitly required for legitimate use cases.

Recommended fix Moderate confidence

Grafana Snowflake datasource plugin version >= 1.14.13

  1. 1. Identify the Grafana instance running the Snowflake datasource plugin versions 1.14.7 through 1.14.12
  2. 2. Upgrade the Grafana Snowflake datasource plugin to version 1.14.13 or later
  3. 3. Verify the upgrade was successful by checking the plugin version in Grafana under Configuration > Plugins
  4. 4. Test that Snowflake datasource queries still function correctly after the upgrade
  5. 5. Review user permissions on the Snowflake datasource to ensure only necessary users have query access

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

Fix this in Snowflake Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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