A service account with user-management permissions in one organization can read, modify, disable or delete users belonging to other organizations on the same Grafana instance through the SCIM API (insecure direct object reference). Only Grafana Enterprise instances with SCIM enabled are affected.
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 rules API (/loki/api/v1/rules), allowing them to create, modify and delete Loki alerting rules. Because those rules are stored by Loki rather than by Grafana, the change took effect for every user of that Loki data source, not only for the Viewer who made the request.
Exploitation requires an authenticated Viewer account on the Grafana instance and a configured Loki data source; no other privileges are needed. Both Grafana OSS and Grafana Enterprise are affected. The defect is in Grafana's data source proxy; Loki itself is not vulnerable and does not need to be patched.
CVE-2026-33374 is a vulnerability in Grafana Enterprise affecting the Prometheus rule conversion API endpoints. These endpoints do not limit the size of the request body, allowing authenticated users to cause unbounded memory allocations. This can lead to out-of-memory conditions that crash the server. The vulnerability affects multiple versions of Grafana Enterprise from 12.0.0 through versions prior to 12.3.12, 12.4.0 through prior to 12.4.13, 13.0.0 through prior to 13.0.11, 13.1.0 through prior to 13.1.8, and 13.2.0 through prior to 13.2.4. The CVSS score is 6.5, indicating a medium severity impact focused on availability disruption.
CVE-2026-15577 is a medium severity vulnerability in Grafana Enterprise where a user or service account with read-only access to Git Sync provisioning connections can improperly modify a connection's configuration via its status subresource due to incorrect authorization. This issue affects specific versions of Grafana Enterprise when the experimental provisioning feature toggle is enabled. The vulnerability has a CVSS score of 6.5 and does not impact confidentiality or availability but allows integrity modification. No known exploits are reported, and no official patch links are provided.
CVE-2026-93294 is a vulnerability in Grafana Enterprise where a user with query access to an Azure Monitor data source can misuse the resource proxy to call Azure Resource Manager APIs beyond intended scope using the data source's Azure identity. The impact depends on the Azure role assigned to that identity. A patch is available to address this issue.
CVE-2026-95502 is a vulnerability in Grafana Nanogit where a Git server used by Grafana's Git Sync provisioning can cause uncontrolled resource consumption by returning oversized or highly compressed responses. This can exhaust Grafana's memory. Exploitation requires that an administrator has configured Git Sync to use the vulnerable Git server. The vulnerability affects multiple version ranges of Grafana Nanogit and has a medium severity rating with a CVSS score of 5.3.
CVE-2026-89039 is a path traversal vulnerability in Grafana's mcp-k6 component that allows an authenticated caller with limited privileges to read arbitrary files on the server. By invoking the convert_playwright_script prompt and passing a crafted file path, an attacker can bypass directory restrictions using symbolic links and access sensitive files such as SSH keys and cloud credentials. This vulnerability affects versions 0.3.0 through before 0.7.0 of mcp-k6.
An Editor can set file-provisioning metadata (the grafana.app/managedBy, grafana.app/managerId and grafana.app/sourcePath annotations) when creating a dashboard through the dashboard API, because these fields were stored without an authorization check. The dashboard then appears file-provisioned, and administrators can no longer update or delete it through Grafana. The impact is limited to the same organization and no data is exposed.
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.
CVE-2026-81841 is a medium severity vulnerability in Grafana Enterprise where pausing a shared public dashboard does not revoke its access token for frontend bootstrap data endpoints. This allows anyone with the link to the paused dashboard to retrieve its data source configuration, including stored credentials for browser-accessible data sources, without authentication. Deleting the shared dashboard properly revokes the token and prevents access.
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.
CVE-2026-76154 is a stored cross-site scripting (XSS) vulnerability in the Geomap panel's MapLibre base layer of Grafana OSS. It allows a user with the Editor role to execute arbitrary JavaScript in another user's session by hosting a malicious style configuration. This can lead to escalation of privileges to Org Admin. The vulnerability affects multiple versions of Grafana OSS, with a CVSS score of 7.3 indicating high severity.
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 identities could collide on one key. An authenticated user who shapes their own attributes to collide with a higher-privileged user's, while that user's cache entry is live, is authenticated as that user, up to Administrator (authentication bypass by spoofing).
When SAML IdP-initiated login is enabled in Grafana Enterprise, the SAML library skips validation of the InResponseTo field on all SAML responses, including SP-initiated logins. This removes anti-replay protection, allowing an attacker who obtains a valid signed SAML assertion to replay it and gain a session as the victim user. Only instances with the allow_idp_initiated SAML setting enabled are affected; this setting is off by default and Grafana OSS is not affected.
An authenticated user with permission to query a SQL data source can bypass the fix for CVE-2026-33375 by injecting the timeGroup macro through a WHERE clause, which Grafana's regex-based macro parsing does not reject. Evaluating the injected macro causes uncontrolled memory consumption that can terminate the Grafana server process, resulting in a denial of service. The Microsoft SQL Server, PostgreSQL, and MySQL data sources are affected.
CVE-2026-75889 is a high-severity vulnerability in Grafana Alloy version 1.0.0 affecting the prometheus.operator.servicemonitors component. It allows an attacker with the ability to create or modify ServiceMonitor resources in a watched namespace to specify an arbitrary local file via bearerTokenFile. Alloy reads this file and sends its contents as a bearer token to an attacker-controlled scrape endpoint, potentially disclosing sensitive files such as the Kubernetes service account token. Exploitation requires write access to ServiceMonitor resources and privileges lower than Alloy's service account.