Vulnerabilities

Only self-managed Grafana instances with Auth Proxy authentication and identity caching enabled (sync_ttl greater than zero) are affected.

A user with Editor permissions can craft a dashboard whose table (TableNG) panel contains a malicious field name that executes as a script in the browser of any user who views the dashboard (stored cross-site scripting).

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).

Several Grafana API endpoints, some of them unauthenticated, do not limit the size of the request body before processing it.

The public dashboard deletion endpoint does not enforce organization isolation, allowing an Org Admin in one organization to delete public dashboards belonging to a different organization by supplying the target dashboar…

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.

A user with Editor permissions can place a malicious script in the attribution field of a Geomap panel's XYZ tile layer via a template variable.

A user with Viewer permissions can use specially crafted requests to the Tempo and Loki data source plugins to reach unintended backend endpoints.

Editors could delete any annotation, even those they do not have read access to.

Using the $__timeGroup macro, one can achieve an OOM by overloading the server.

A request to the Grafana plugin resources endpoint can cause unbounded memory allocation by reading the entire request body into memory.

When using an IPv6 allow-list for the Auth Proxy feature, it defaults to /32 addresses.

A vulnerability in SQL Expressions allows an authenticated attacker to read arbitrary files from the Grafana server's filesystem.

Any Editor could delete any snapshot, even if they have no access to read or write them.

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.

An Editor can overwrite a dashboard not owned by them to acquire admin on that specific dashboard.

The Grafana Live push endpoint can be exploited to cause unbounded memory allocation by sending a large or streaming request body, potentially leading to out-of-memory conditions.

A race condition in Grafana Live allows authenticated users with Viewer role to trigger a server crash by sending concurrent requests that cause a fatal map access error.

A cross-tenant isolation vulnerability was found in Grafana’s Correlations feature affecting legacy correlation records.

In Grafana's alerting system, users with edit permissions for a contact point, specifically the permissions “alert.notifications:write” or “alert.notifications.receivers:test” that are granted as part of the fixed role "…

A resample query can be used to trigger out-of-memory crashes in Grafana.

A testdata data-source can be used to trigger out-of-memory crashes in Grafana.

A chained attack via SQL Expressions and a Grafana Enterprise plugin can lead to a remote arbitrary code execution impact (RCE).

The OpenFeature feature toggle evaluation endpoint reads unbounded values into memory, which can cause out-of-memory crashes.

When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards.