Grafana vulnerable to authenticated users bypassing dashboard, folder permissions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-3260: 0.56% estimated exploitation activity in the next 30 days; percentile 46.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A security vulnerability in the /apis/dashboard.grafana.app/ endpoints allows authenticated users to bypass dashboard and folder permissions. The vulnerability affects all API versions (v0alpha1, v1alpha1, v2alpha1). Impact: - Viewers can view all dashboards/folders regardless of permissions - Editors can view/edit/delete all dashboards/folders regardless of permissions - Editors can create dashboards in any folder regardless of permissions - Anonymous users with viewer/editor roles are similarly affected Organization isolation boundaries remain intact. The vulnerability only affects dashboard access and does not grant access to datasources.

Published by the source

2 Jun 2025, 12:30 UTC

Last modified by the source

5 Jun 2025, 01:04 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3px7-c4j3-576r

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

# Patch Next advisory brief: CVE-2025-3260

Advisory: Grafana vulnerable to authenticated users bypassing dashboard, folder permissions
IDs: CVE-2025-3260, GHSA-3px7-c4j3-576r
Record: https://patchnext.com/advisories/cve-2025-3260 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
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 0.0.0-20250521183405-c7a690348df7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/grafana: affected >= 0.0.0-20250114093457-36d6fad421fb, < 0.0.0-20250521183405-c7a690348df7; fixed in 0.0.0-20250521183405-c7a690348df7

## 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-3px7-c4j3-576r (GitHub-reviewed advisory GHSA-3px7-c4j3-576r lists affected ranges: Go github.com/grafana/grafana >=0.0.0-20250114093457-36d6fad421fb <0.0.0-20250521183405-c7a690348df7)

Commands are suggestions: review each one before running it.