dbcve.org
GrafanaApplication

CVE-2026-28380

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
Any Editor could delete any snapshot, even if they have no access to read or write them.

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

This is a broken access control vulnerability where the snapshot deletion function lacks proper authorization checks. An Editor role user can delete any snapshot object via direct object reference, even when they have no read or write permissions to that specific snapshot. The delete operation bypasses permission validation, allowing unauthorized data destruction.

MitigationImplement and enforce proper authorization checks on all snapshot deletion endpoints to verify the user has appropriate permissions (delete access) before allowing the operation. Consider adopting a deny-by-default permission model.

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.5.0, < 11.6.14>= 12.2.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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 installed Grafana version
    Run 'grafana-cli --version' or 'grafana-server --version', or check the Grafana health API at /api/health. If CLI tools are unavailable, inspect the installed package via your package manager (dpkg, rpm, brew, or docker inspect).
    Affected if The installed version falls within any of these ranges: >= 8.5.0 and < 11.6.14, >= 12.2.0 and < 12.2.8, >= 12.3.0 and < 12.3.6, >= 12.4.0 and < 12.4.3, or equals exactly 11.6.14, 12.2.8, 12.3.6, 12.4.3, 13.0.0, or 13.0.1.
  2. Verify snapshot feature is enabled
    Check Grafana configuration files (grafana.ini or custom.ini) for the [snapshots] section. Look for the 'external_enabled' or 'enabled' setting. Alternatively, query the Grafana Configuration API (GET /api/admin/settings) if accessible and check for snapshot-related settings.
    Affected if Snapshots are enabled (external_enabled = true or enabled = true) in the configuration.
  3. Confirm snapshot deletion API is accessible
    Attempt a GET request to the snapshot API (such as /api/snapshots or /api/dashboards/snapshots) using an authenticated session with Editor role. Note: This is an observation check only, not an exploitation test. Check Grafana logs or API documentation for endpoint availability.
    Affected if The snapshot API endpoints are reachable and respond to authenticated requests from Editor role users.
  4. Review user permissions on existing snapshots
    List all snapshots via the API (GET /api/dashboards/snapshots) and examine the metadata for each snapshot to identify which users or roles have delete permissions assigned. Cross-reference with the Grafana User and Team permissions UI for the dashboard associated with each snapshot.
    Affected if Snapshots exist in the system where some Editor users have no read or write permissions assigned yet the snapshot deletion API remains accessible to them.

A user is affected if their Grafana version is within the affected ranges listed AND the snapshot feature is enabled, allowing unauthorized deletion of snapshots by Editor users who lack proper permissions on those specific snapshot objects.

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

Implement and enforce proper authorization checks on all snapshot deletion endpoints to verify the user has appropriate permissions (delete access) before allowing the operation. Consider adopting a deny-by-default permission model.

Recommended fix High confidence

11.6.14 (or latest 11.x stable; alternatively 12.2.8/12.3.6/12.4.3 or later depending on branch)

  1. 1. Backup your Grafana configuration and data
  2. 2. Review Grafana upgrade notes for your target version for any breaking changes
  3. 3. Upgrade Grafana to version 11.6.14 or later (recommended: latest 11.x stable release)
  4. 4. Alternatively, upgrade to version 12.2.8, 12.3.6, or 12.4.3 or later depending on your current major version
  5. 5. After upgrade, verify that Editor role can no longer delete snapshots they don't have access to
  6. 6. Test snapshot deletion permissions to confirm authorization is properly enforced
Caveat Review Grafana release notes for breaking changes between your current and target version 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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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