Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1

Grafana: Users outside an organization can delete a snapshot with its key

CVE-2024-1313GHSA-67rv-qpw2-6qrr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/grafana/grafana 10.3.5, 10.2.6, 10.1.9, 10.0.13, 9.5.18), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/grafana/grafana

    Affected
    >= 9.5.0, < 9.5.18>= 10.0.0, < 10.0.13>= 10.1.0, < 10.1.9>= 10.2.0, < 10.2.6>= 10.3.0, < 10.3.5
    Fixed in
    10.1.9, 10.0.13, 9.5.18, 10.3.5, 10.2.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-1313: 0.65% estimated exploitation activity in the next 30 days; percentile 51.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The DELETE /api/snapshots/{key} endpoint allows any Grafana user to delete snapshots if the user is NOT in the organization of the snapshot Details An attacker (a user without organization affiliation or with a "no basic role" in an organization other than the one where the dashboard exists), knowing the key or URL of a snapshot created by any user (including Grafana admins), can delete a snapshot (It is not feasible using UI), resulting in a BOLA vulnerability. If an attacker is in the same organization of the dashboard snapshot, he can’t delete the snapshot. However, an attacker with low-privilege from a different organization would be able to delete it, resulting in the authorization flaw. Precondition To exploit this endpoint, an attacker must know the {key} of a snapshot. The attacker can potentially discover this key in various ways. When creating a snapshot through the API, users can manually specify a key without any complexity requirements. This lack of complexity…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-67rv-qpw2-6qrr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-1313

Advisory: Grafana: Users outside an organization can delete a snapshot with its key
IDs: CVE-2024-1313, GHSA-67rv-qpw2-6qrr
Record: https://patchnext.com/advisories/cve-2024-1313 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/grafana/grafana 10.3.5, 10.2.6, 10.1.9, 10.0.13, 9.5.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/grafana: affected >= 9.5.0, < 9.5.18; >= 10.0.0, < 10.0.13; >= 10.1.0, < 10.1.9; >= 10.2.0, < 10.2.6; >= 10.3.0, < 10.3.5; fixed in 10.1.9, 10.0.13, 9.5.18, 10.3.5, 10.2.6

## Suggested inspection (read-only)
- Go github.com/grafana/grafana: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/grafana/grafana.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-67rv-qpw2-6qrr (GitHub-reviewed advisory GHSA-67rv-qpw2-6qrr lists affected ranges: Go github.com/grafana/grafana >=9.5.0 =10.0.0 =10.1.0 =10.2.0 =10.3.0 <10.3.5)

Commands are suggestions: review each one before running it.

Loading voting…