Grafana OSS vulnerabilities, page 2

38 vulnerabilities

Known vulnerabilities in Grafana OSS, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

6.5CVE-2026-28380chainguardgrafana-12.0+9
EPSS score
0.23%
Any Editor could delete any snapshot, even if they have no access to read or write them.
3.1CVE-2026-28378grafanagrafana+2
EPSS score
0.23%
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 dashboard's identifiers.
4.3CVE-2026-28374chainguardgrafana-12.0+9
EPSS score
0.20%
Editors could delete any annotation, even those they do not have read access to. The editor user cannot create or read the annotations.
6.5CVE-2026-28376chainguardgrafana-12.0+9
EPSS score
0.33%
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. An authenticated user with access to the Grafana Live API can trigger this issue.
6.5CVE-2026-28379chainguardgrafana-12.0+9
EPSS score
0.26%
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. This results in complete service unavailability requiring restart of the Grafana server.
6.5CVE-2026-28383chainguardgrafana-12.0+9
EPSS score
0.33%
A request to the Grafana plugin resources endpoint can cause unbounded memory allocation by reading the entire request body into memory. An authenticated user can exploit this to trigger an out-of-memory condition, potentially causing a denial of service.
5.3CVE-2026-81841chainguardgrafana-11.6+8
EPSS score
0.37%
Pausing a shared (public) dashboard did not revoke its access token for the endpoints that serve frontend bootstrap data. Anyone holding the link to a paused shared dashboard could still retrieve, without authenticating, the configuration of the dashboard's data sources, including stored credentials for data sources using browser access (missing authorization). Deleting the shared dashboard does revoke the token.
4.3CVE-2026-81842chainguardgrafana-12.2+6
EPSS score
0.20%
An authenticated user with edit permission on one folder can move a library panel into another folder where they only have view permission, through the library elements API or the equivalent App Platform resource. The update path did not check library panel create permission on the destination folder (incorrect authorization). No data from the destination folder is disclosed, and existing content there cannot be changed.
8.8CVE-2026-15815chainguardgrafana-11.6+6
EPSS score
0.69%
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 backend binary outside that directory. The dropped executable runs with the privileges of the Grafana server process, resulting in remote code execution. Plugin archives are extracted before their signature is verified, so a valid plugin signature does not prevent the write. An operator can therefore be affected by installing a plugin that appears legitimate, as well as by installing a plugin from an arbitrary archive using grafana-cli, the GF_INSTALL_PLUGINS environment variable, or preinstall configuration. Grafana Enterprise is affected because it includes the same plugin extraction code as Grafana OSS.
6.8CVE-2026-8595grafanagrafana+1
EPSS score
0.30%
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).
7.5CVE-2026-8609grafanagrafana+1
EPSS score
0.48%
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.5CVE-2026-33382grafanagrafana+2
EPSS score
0.39%
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 service.
8.1CVE-2026-33381chainguardgrafana-12.0+15
EPSS score
0.33%
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.4CVE-2026-33376chainguardgrafana-12.0+9
EPSS score
0.28%
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, LDAP, etc are unaffected here.
6.5CVE-2026-33380chainguardgrafana-12.0+15
EPSS score
0.35%
A vulnerability in SQL Expressions allows an authenticated attacker to read arbitrary files from the Grafana server's filesystem. Only instances with the sqlExpressions feature toggle enabled are vulnerable.
7.1CVE-2026-33377chainguardgrafana-12.0+9
EPSS score
0.23%
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.
6.5CVE-2026-33378chainguardgrafana-12.0+9
EPSS score
0.33%
Using the $__timeGroup macro, one can achieve an OOM by overloading the server. This requires a SQL datasource. If the server is set up to auto-restart, the impact is minimal or non-existent, as the attack can take upwards of half an hour to crash the server.
6.5CVE-2026-33375chainguardgrafana-fips-12.1+4
EPSS score
0.48%
The Grafana MSSQL data source plugin contains a logic flaw that allows a low-privileged user (Viewer) to bypass API restrictions and trigger a catastrophic Out-Of-Memory (OOM) memory exhaustion, crashing the host container.