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.
| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/grafana/grafana | ≥ 8.0.0-beta1, < 8.0.7≥ 8.1.0, < 8.1.8≥ 8.2.0, < 8.2.7≥ 8.3.0, < 8.3.1 | 8.0.78.1.88.2.78.3.1 |
| grafana | = 8.0.0= 8.3.0≥ 8.0.1, < 8.0.7≥ 8.1.0, < 8.1.8≥ 8.2.0, < 8.2.7 | 8.0.78.1.88.2.7 |
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.
Release v8.3.1, only containing a security fix:
Release v8.2.7, only containing a security fix:
Release v8.1.8, only containing a security fix:
Release v8.0.7, only containing a security fix:
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:
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
Grafana 8.0.0-beta1 to 8.3.0
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.
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
We would like to thank Jordy Versmissen for finding the vulnerability and alerting us to it.
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
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from keyserver.ubuntu.com.
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.
You can also subscribe to our RSS feed.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free