CVE-2025-3260

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2025-3260 has a CVSS score of 8.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20250521183405-c7a690348df7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-3260? CVE-2025-3260 is a high-severity incorrect authorization vulnerability in github.com/grafana/grafana (go), affecting versions >= 0.0.0-20250114093457-36d6fad421fb, < 0.0.0-20250521183405-c7a690348df7. It is fixed in 0.0.0-20250521183405-c7a690348df7. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2025-3260? CVE-2025-3260 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/grafana/grafana are affected by CVE-2025-3260? github.com/grafana/grafana (go) versions >= 0.0.0-20250114093457-36d6fad421fb, < 0.0.0-20250521183405-c7a690348df7 is affected.
4. Is there a fix for CVE-2025-3260? Yes. CVE-2025-3260 is fixed in 0.0.0-20250521183405-c7a690348df7. Upgrade to this version or later.
5. Is CVE-2025-3260 exploitable, and should I be worried? Whether CVE-2025-3260 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-3260 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-3260? Upgrade github.com/grafana/grafana to 0.0.0-20250521183405-c7a690348df7 or later.