CVE-2025-3260VulnerabilityPublished 2 Jun 2025

CVE-2025-3260: Grafana · CWE-863

Affects GrafanaSource CVE Database V5

Not known to be exploited · CVSS 8.3 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Grafana Grafana	Affected =11.6.0	Fixed in–

AI-suggested

To mitigate the risks posed by CVE-2025-3260, European organizations should take immediate and specific actions beyond generic advice: 1) Upgrade Grafana to a version where this vulnerability is patched as soon as an official fix is released. Monitor Grafana’s official channels for patch announcements. 2) Until a patch is available, restrict access to the affected API endpoints by implementing network-level controls such as firewall rules or API gateways that limit access to trusted users and systems only. 3) Review and tighten user role assignments within Grafana, minimizing the number of users with editor roles and ensuring anonymous access is disabled or strictly controlled. 4) Implement enhanced monitoring and alerting on dashboard and folder changes to detect unauthorized modifications promptly. 5) Use Grafana’s audit logs to track access and changes to dashboards and folders, enabling forensic analysis if unauthorized activity is suspected. 6) Consider isolating critical dashboards in separate Grafana instances or environments to reduce the blast radius. 7) Educate administrators and users about the vulnerability and the importance of adhering to the principle of least privilege. These measures will help reduce the attack surface and limit potential damage until the vulnerability is fully remediated.

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.

Impact

For European organizations, the impact of CVE-2025-3260 can be substantial, especially for those relying heavily on Grafana for monitoring IT infrastructure, business metrics, and operational dashboards. Unauthorized access to dashboards can lead to exposure of sensitive operational data, business intelligence, and potentially personally identifiable information if such data is visualized. Editors gaining unauthorized write and delete permissions can lead to data integrity issues, including the alteration or removal of critical dashboards, which may disrupt monitoring and incident response activities. Although datasource access is not compromised, the ability to manipulate dashboards can still facilitate misinformation, hinder decision-making, and potentially mask ongoing attacks or failures. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and critical infrastructure, may face compliance risks and reputational damage if sensitive information is exposed or manipulated. The vulnerability also poses risks to multi-tenant environments where dashboards are segregated by folder permissions, as unauthorized cross-folder access could violate data segregation policies. Given the widespread use of Grafana in Europe, this vulnerability could affect a broad range of industries and organizations.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

grafana.com/security/security-advisories/CVE-2025-3260/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 12:56 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats