# CVE-2025-3260: Grafana vulnerable to authenticated users bypassing dashboard, folder permissions

> Authenticated users can bypass dashboard and folder permissions to view, edit, or delete resources they should not access.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** BIT-grafana-2025-3260, GHSA-3px7-c4j3-576r, GO-2025-3740, MINI-2hh9-6p5f-55rm, MINI-4973-8xfh-f74p, MINI-4h2w-6rwm-qcpr, MINI-5gwq-fh96-h4cv, MINI-885m-4xvp-v7vq, MINI-9p3g-7fvv-vvm5, MINI-fvpf-7x4f-p3m7, MINI-g789-4jw4-28f4, MINI-ggq3-mpvm-82mh, MINI-gqmj-p8p7-4mx2, MINI-h4rw-wp2q-wvxc, MINI-h97r-p895-8p73, MINI-q23j-6jm5-q5jq, MINI-rwjv-26q3-8f47, MINI-w8vh-cr3j-898f, MINI-wpgp-qhrx-4hr6, MINI-xcj6-5jqx-3xc6, UBUNTU-CVE-2025-3260

## What is CVE-2025-3260?

CVE-2025-3260 is a high-severity missing authorization vulnerability in Grafana, published on 2 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-3260?

4 open source packages ship an affected version, including github.com/grafana/grafana and grafana.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | From 0.0.0-20250114093457-36d6fad421fb | None |
| `github.com/grafana/grafana` | Go | From 0.0.0-20250114093457-36d6fad421fb | 0.0.0-20250521183405-c7a690348df7 |
| `github.com/grafana/grafana` | Go | From 0.0.0-20250114093457-36d6fad421fb | 0.0.0-20250521183405-c7a690348df7 |
| `grafana` | Bitnami | From 11.6.0 | 11.6.1 |

## How do I fix CVE-2025-3260?

Upgrade github.com/grafana/grafana to 0.0.0-20250521183405-c7a690348df7 or later.

## Is CVE-2025-3260 being exploited?

There is no known exploitation of CVE-2025-3260 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3260 and fix it if it is affected.

What it is: CVE-2025-3260 is a high-severity missing authorization vulnerability in Grafana, published on 2 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3260 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected from 0.0.0-20250114093457-36d6fad421fb; no fix listed
- github.com/grafana/grafana (Go): affected from 0.0.0-20250114093457-36d6fad421fb; fixed in 0.0.0-20250521183405-c7a690348df7
- github.com/grafana/grafana (Go): affected from 0.0.0-20250114093457-36d6fad421fb; fixed in 0.0.0-20250521183405-c7a690348df7
- grafana (Bitnami): affected from 11.6.0; fixed in 11.6.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3260/ (Markdown: https://insights.sbomify.com/CVE-2025-3260/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3260
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3260
- OSV: https://osv.dev/vulnerability/CVE-2025-3260

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3260/
Summaries are generated and may contain mistakes; the official description above is the record.