Grafana vulnerabilities
We track 69 vulnerabilities in Grafana products across 30 products. 68 are rated high or critical, and 2 have been exploited in real attacks. The most recent was published on November 12, 2026.
Latest Grafana vulnerabilities
- 7.1 High severity
Elasticsearch Datasource: Improper Limitation of a Pathname to a Restricted Directory
The Elasticsearch data source resource proxy forwards the request method and path to Elasticsearch using the data source's own credentials, without restricting them to the operations the plugin needs. A user who can query the data source can alter index mappin
- 7.1 High severity
Grafana Enterprise: Exposure of Sensitive Information to an Unauthorized Actor
A user with the Viewer or Editor role could bypass folder permissions on Git Sync managed resources through the repository files API: a Viewer could read files in folders they could not access, and an Editor could create, modify, move or delete provisioned das
- 7.1 High severity
Grafana Enterprise: Improper Privilege Management
A user with the Editor role who can edit a folder can move it, through the folders resource API, under a folder they administer, and so gain Admin on the moved folder and its contents, including the right to change their permissions. The legacy folder move API
- 7.1 High severity
Grafana OSS: Exposure of Sensitive Information to an Unauthorized Actor
When independent Grafana instances share the same [rendering] renderer_token, an image renderer key issued by one instance is accepted by the others, so a user on one instance could act as the user with the same ID on another (origin validation error). This af
- 8.5 High severity
Grafana OSS: Missing Authorization
A user with any role, including Viewer or a service account with no permissions, can create, externally publish, and delete dashboard snapshots (missing authorization). Only Grafana OSS and Grafana Enterprise 12.4 are affected; earlier versions and Grafana 13
- 7.7 High severity
Enterprise Metrics (GEM): Improper Limitation of a Pathname to a Restricted Directory
Grafana Mimir's Alertmanager rejects tenant-supplied receiver configurations that reference local files, but the check did not cover two HTTP client settings: http_headers.<name>.files and basic_auth.username_file. A tenant permitted to upload an Alertmanager
- 7.7 High severity
A user with query access to an Azure Monitor data source in Grafana can cause server-side…
A user with query access to an Azure Monitor data source in Grafana can cause server-side requests to an attacker-controlled endpoint that disclose the data source's Azure access token (server-side request forgery).
- 8.9 High severity
Grafana Enterprise: Improper Authorization
An authenticated user in Grafana can read SSO client secrets and modify instance-wide SSO settings without the required permissions (missing authorization). This affects Grafana OSS and Enterprise 13.2 installations with the experimental kubernetesSsoSettingsA
- 7.7 High severity
Grafana Enterprise: Incorrect Authorization
A user with permission to edit contact points but not their protected fields can change protected settings, such as a contact point's destination URL, by switching an integration to a legacy schema version, which can expose stored credentials and redirect aler
- 7.1 High severity
Grafana Enterprise: Improper Access Control
Grafana's data source proxy did not apply role-based access control to write requests forwarded to Loki data sources. A user holding only the Viewer role on an affected Grafana instance could send POST, PUT and DELETE requests through the proxy to the Loki rul
- 7.3 High severity
Grafana OSS: Improper Neutralization of Input During Web Page Generation
A stored cross-site scripting vulnerability in the Geomap panel's MapLibre base layer allows a user with the Editor role to execute arbitrary JavaScript in another user's session by hosting a malicious style configuration, enabling escalation to Org Admin.
- 8.8 High severity
Grafana OSS: Improper Limitation of a Pathname to a Restricted Directory
Grafana OSS and Grafana Enterprise did not safely resolve symbolic links when extracting plugin archives. A crafted plugin archive can chain relative symbolic link entries to escape the plugin installation directory, writing arbitrary files and an executable b
- 8.1 High severity
Grafana Enterprise: Authentication Bypass by Spoofing
Only self-managed Grafana instances with Auth Proxy authentication and identity caching enabled (sync_ttl greater than zero) are affected. The Auth Proxy cache key concatenated the username and forwarded identity attributes without a delimiter, so distinct ide
- 7.7 High severity
Alloy: Files or Directories Accessible to External Parties
Grafana Alloy’s prometheus.operator.servicemonitors component allows a user who can create or modify ServiceMonitor resources in a watched namespace to specify an arbitrary local file through bearerTokenFile. Alloy reads the file and sends its contents as a be
- 7.1 High severity
Grafana OSS: Incorrect Authorization
An authenticated user with permission to create or edit alert rules can bypass datasource query authorization by marking an alert rule query as a server-side expression while referencing a real datasource UID (incorrect authorization). This can expose data acc
- 9.1 Critical severity
Grafana MCP Server: Server-Side Request Forgery
A caller-supplied X-Grafana-URL request header controls the destination of mcp-grafana's outbound requests, and the grafana_api_request tool lets the caller also choose the HTTP method, path, and body. Because the destination is not restricted to the configure
- 7.1 High severity
Grafana IRM: Improper Access Control
Note: The CVE and blog post don't exist because we determined this is actually a cloud-only issue. Access Controls are “Broken” when a user can access resources they are not authorized to access. An attacker can bypass any access control mechanisms in a web ap
- 7.5 High severity
Loki: Allocation of Resources Without Limits or Throttling
Loki queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy.
- 8.6 High severity
Grafana MCP Server: Externally Controlled Reference to a Resource in Another Sphere
A confused-deputy flaw in Grafana MCP Server allows an unauthenticated remote attacker to exfiltrate the server's environment-configured Grafana service-account token by supplying a crafted X-Grafana-URL request header. This also enables SSRF against arbitrary
- 7.5 High severity
Grafana OSS: Uncontrolled Resource Consumption
An unauthenticated attacker can repeatedly call Grafana's OAuth login route with unique values, causing unbounded memory growth that can eventually exhaust memory and crash the Grafana instance (denial of service).
- 7.5 High severity
Grafana OSS: Uncontrolled Resource Consumption
Several Grafana API endpoints, some of them unauthenticated, do not limit the size of the request body before processing it. An attacker can send very large payloads that force excessive memory allocation, potentially exhausting memory and causing a denial of
- 7.5 High severity
Grafana Enterprise: Uncontrolled Resource Consumption
The public dashboard query endpoint does not limit request body size before processing, allowing unauthenticated attackers to trigger excessive memory allocation by sending arbitrarily large JSON payloads. This can lead to denial of service through memory exha
- 7.7 High severity
Grafana OSS: Improper Limitation of a Pathname to a Restricted Directory
A user with Viewer permissions can use a path traversal in the Loki data source plugin to reach administrative Loki endpoints and read sensitive backend configuration and internal service information.
- 8.1 High severity
Snowflake Datasource: Improper Access Control
The Snowflake datasource allows for GET/PUT commands, which can allow any user with access to run queries against the data source to read/write files between the local grafana server and the connected Snowflake host.
- 8.8 High severity
Grafana Operator: Improper Limitation of a Pathname to a Restricted Directory
We have released version 5.24.0 of the Grafana Operator. This patch includes a MEDIUM severity security fix for a path traversal/privilege escalation vulnerability in the Grafana Operator. ### Summary The Grafana Operator supports loading dashboards & library
- 8.1 High severity
Grafana OSS: Improper Access Control
When a user's access to mint tokens for a service account is revoked, it is sometimes still possible to do so for a few seconds after the event. The user will eventually lose access to do this.
- 7.1 High severity
Grafana OSS: Improper Authentication
An Editor can overwrite a dashboard not owned by them to acquire admin on that specific dashboard. The user must have write access to the dashboard to escalate privilege.
- 7.4 High severity
Grafana OSS: Initialization of a Resource with an Insecure Default
When using an IPv6 allow-list for the Auth Proxy feature, it defaults to /32 addresses. Addresses specifying a mask explicitly are not affected; to mitigate easily, add the desired mask (usually /128) to the addresses. Only auth proxy is affected; Okta, SAML,
- 7.5 High severity
Tempo: Uncontrolled Resource Consumption
Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternati
- 9.1 Critical severity
Pyroscope: Incorrect Permission Assignment for Critical Resource
Pyroscope is an open-source continuous profiling database. The database supports various storage backends, including Tencent Cloud Object Storage (COS). If the database is configured to use Tencent COS as the storage backend, an attacker could extract the secr
- 7.5 High severity
Grafana: Cleartext Storage of Sensitive Information
When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards. No passwords of proxied data-sources are exposed. We encourage all direct data-sources to be converted to proxied data-so
- 9.1 Critical severity
Grafana: Improper Control of Generation of Code
A chained attack via SQL Expressions and a Grafana Enterprise plugin can lead to a remote arbitrary code execution impact (RCE). This is enabled by a feature in Grafana (OSS), so all users are always recommended to update to avoid future attack vectors going t
- 7.5 High severity
Tempo: Inadequate Encryption Strength
A vulnerability in Grafana Tempo exposes the S3 SSE-C encryption key in plaintext through the /status/config endpoint, potentially allowing unauthorized users to obtain the key used to encrypt trace data stored in S3. Thanks to william_goodfellow for reporting
- 8.1 High severity
grafana/grafana: Incorrect Authorization
The dashboard permissions API does not verify the target dashboard scope and only checks the dashboards.permissions:* action. As a result, a user who has permission management rights on one dashboard can read and modify permissions on other dashboards. This is
- 7.5 High severity
grafana/grafana-enterprise: Uncontrolled Resource Consumption
Every uncached /avatar/:hash request spawns a goroutine that refreshes the Gravatar image. If the refresh sits in the 10-slot worker queue longer than three seconds, the handler times out and stops listening for the result, so that goroutine blocks forever try
- 9.8 Critical severity
Grafana Enterprise: Incorrect Privilege Assignment
SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management. In Grafana versions 12.x where SCIM provisioning is enabled and
- 9.9 Critical severity
grafana-image-renderer: Improper Control of Generation of Code
Grafana Image Renderer is vulnerable to remote code execution due to an arbitrary file write vulnerability. This is due to the fact that the /render/csv endpoint lacked validation of the filePath parameter that allowed an attacker to save a shared object to an
- 7.6 High severity
Grafana: Improper Neutralization of Input During Web Page Generation
An open redirect vulnerability has been identified in Grafana OSS that can be exploited to achieve XSS attacks. The vulnerability was introduced in Grafana v11.5.0. The open redirect can be chained with path traversal vulnerabilities to achieve XSS. Fixed in v
- 8.3 High severity
Grafana: Incorrect Authorization
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/
- 8.8 High severity
Grafana: Improper Neutralization of Special Elements used in a Command
The SQL Expressions experimental feature of Grafana allows for the evaluation of `duckdb` queries containing user input. These queries are insufficiently sanitized before being passed to `duckdb`, leading to a command injection and local file inclusion vulnera