Grafana Path Traversal Vulnerability. Actively exploited: CISA added this vulnerability to its Known Exploited Vulnerabilities catalog on 09/10/2025. Patch affected systems as an emergency.
요약
CVE-2021-43798은(는) github.com/grafana/grafana, grafana (grafana)에 영향을 주는 높음 (CVSS 7.5) 취약점입니다.
Today we are releasing Grafana 8.3.1, 8.2.7, 8.1.8, 8.0.7. This patch release includes a high severity security fix that affects Grafana versions from v8.0.0-beta1 through v8.3.0.
On 2021-12-03, we received a report that Grafana is vulnerable to directory traversal, allowing access to local files. We have confirmed this for versions 8.0.0-beta1 to 8.3.0. Thanks to our defense-in-depth approach, at no time has Grafana Cloud been vulnerable.
The vulnerable URL path is: <grafana_host_url>/public/plugins/<plugin-id>/, where <plugin-id> is the plugin ID for any installed plugin.
Every Grafana instance comes with pre-installed plugins like the Prometheus plugin or MySQL plugin so the following URLs are vulnerable for every instance:
CVE-2026-42127높음 7.5The public dashboard query endpoint does not limit request body size before processing, allowing unauthenticated attackers to trigger excess…
CVE-2026-9029보통 5.4A user with Editor permissions can place a malicious script in the attribution field of a Geomap panel's XYZ tile layer via a template varia…
CVE-2026-42129높음 7.7A user with Viewer permissions can use a path traversal in the Loki data source plugin to reach administrative Loki endpoints and read sensi…
CVE-2026-10601보통 4.3A user with Viewer permissions can use specially crafted requests to the Tempo and Loki data source plugins to reach unintended backend endp…
CVE-2026-33381높음 8.1When 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 ev…
We have received CVE-2021-43798 for this issue. The CVSS score for this vulnerability is 7.5 High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) for Grafana versions 8.0.0-beta1 to 8.3.0
Affected versions with high severity
Grafana 8.0.0-beta1 to 8.3.0
Solutions and mitigations
All installations between v8.0.0-beta1 and v8.3.0 should be upgraded as soon as possible.
If you can not upgrade, running a reverse proxy in front of Grafana that normalizes the PATH of the request will mitigate the vulnerability. For example the normalize_path setting in envoy.
Thanks to our defense-in-depth approach, Grafana Cloud instances have not been affected by the vulnerability.
As always, we closely coordinated with all cloud providers licensed to offer Grafana Pro. They have received early notification under embargo and confirmed that their offerings are secure at the time of this announcement. In alphabetical order, this is applicable to Amazon Managed Grafana, and Azure Managed Grafana.
Timeline and postmortem
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
2021-12-03: Security researcher sends the initial report
2021-12-03: Confirmed for 8.0.0-beta1 through 8.3.0
2021-12-03: Confirmed that Grafana Cloud is not vulnerable
2021-12-03: Security fix determined and committed to Git
2021-12-03: Release timeline determined: 2021-12-07 for private customer release, 2021-12-14 for public release
2021-12-06: Second report about the vulnerability received
2021-12-07: We received information that the vulnerability has been leaked to the public, turning it into a 0 day
2021-12-07: Decision made to release as quickly as feasible
2021-12-07: Private release with reduced two hour grace period instead of the usual 1 week
2021-12-07: Public release
Acknowledgements
We would like to thank Jordy Versmissen for finding the vulnerability and alerting us to it.
Reporting security Issues
If you think you have found a security vulnerability, please send a report to [email protected]. This address can be used for all of
Grafana Labs' open source and commercial products (including but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us by using our PGP key. The key fingerprint is
We maintain a security category on our blog, where we will always post a summary, remediation, and mitigation details for any patch containing security fixes.
Grafana is an open-source platform for monitoring and observability. Grafana versions 8.0.0-beta1 through 8.3.0 (except for patched versions) iss vulnerable to directory traversal, allowing access to local files. The vulnerable URL path is: `<grafana_host_url>/public/plugins//`, where is the plugin ID for any installed plugin. At no time has Grafana Cloud been vulnerable. Users are advised to upgrade to patched versions 8.0.7, 8.1.8, 8.2.7, or 8.3.1. The GitHub Security Advisory contains more information about vulnerable URL paths, mitigation, and the disclosure timeline.