# CVE-2022-39201: grafana — Fixed in 8.5.14 🐹 🐹 Go Not in CISA KEV MEDIUM severity # CVE-2022-39201 — grafana MEDIUM [Fix: grafana/grafana@b571acc](https://github.com/grafana/grafana/commit/b571acc1dc130a33f24742c1f93b93216da6cf57) CVE-2022-39201 is a medium-severity (CVSS 6.8) Information Exposure vulnerability in github.com/grafana/grafana. A fix is available for github.com/grafana/grafana — see the affected versions and patch details below. Data source and plugin proxy endpoints could leak the authentication cookie to some destination plugins Also known asBIT-grafana-2022-39201[GHSA-x744-mm8v-vpgr](/vulnerability/GHSA-x744-mm8v-vpgr)GO-2024-2858 Published Oct 13, 2022 Updated Oct 28, 2026 Affected 2 pkgs Patched 2 / 2 Exploits None indexed Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - A successful exploit gives an attacker total control of the affected component, not partial access. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2022-39201. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 1.7%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk 0.40%0.99%1.58%2.17%0.9%1.7%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 2 pkgs affected 🐹`github.com/grafana/grafana`🐹`github.com/grafana/grafana` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems. ## Description Today we are releasing Grafana 9.2. Alongside with new features and other bug fixes, this release includes a Moderate severity security fix for CVE-2022-39201 We are also releasing security patches for Grafana 9.1.8 and Grafana 8.5.14 to fix these issues. Release 9.2, latest release, also containing security fix: - [Download Grafana 9.2](https://grafana.com/grafana/download/9.2) Release 9.1.8, only containing security fix: - [Download Grafana 9.1.8](https://grafana.com/grafana/download/9.1.8) Release 8.5.14, only containing security fix: - [Download Grafana 8.5.14](https://grafana.com/grafana/download/8.5.14) Appropriate patches have been applied to [Grafana Cloud](https://grafana.com/cloud) and 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. This is applicable to Amazon Managed Grafana and Azure's Grafana as a service offering. ### CVE-2022-39201 #### Summary On September 7th as a result of an internal security audit we have discovered that Grafana could leak the authentication cookie of users to plugins. After further analysis the vulnerability impacts data source and plugin proxy endpoints under certain conditions. We believe that this vulnerability is rated at CVSS 6.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H) #### Impact The destination plugin could receive a Grafana authentication cookie of the user. #### Impacted versions All installations for Grafana versions >= v5.0.0-beta1 #### Solutions and mitigations To fully address CVE-2022-39201 please upgrade your Grafana instances. Appropriate patches have been applied to [Grafana Cloud](https://grafana.com/cloud). #### Reporting security issues If you think you have found a security vulnerability, please send a report to [security@grafana.com](mailto:security@grafana.com). 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. #### Security announcements We maintain a [security category](https://community.grafana.com/c/support/security-announcements) 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](https://grafana.com/tags/security/index.xml). ## Affected Packages 2 total 2 fixed Ecosystem Package Vulnerable range Fix 🐹Go `github.com/grafana/grafana` ≥ 5.0.0-beta1&&< 8.5.14 8.5.14`go get github.com/grafana/grafana@v8.5.14` 🐹Go `github.com/grafana/grafana` ≥ 9.0.0&&< 9.1.8 9.1.8`go get github.com/grafana/grafana@v9.1.8` ## Affected Products 1 product · 8 configurations Application `grafana`grafana ≥ 9.0.0 && < 9.1.8 1 version 5.0.0 ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update github.com/grafana/grafana to 8.5.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39201 is resolved across your whole dependency graph. 3. ### Workarounds Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them. ## Fixing This On Your OS If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project. Red HatModerate Product Fixed in Advisory Red Hat Ceph Storage 6.1 `rhceph/rhceph-6-dashboard-rhel9:6-75` [RHSA-2023:3642](https://access.redhat.com/errata/RHSA-2023:3642) Red Hat Enterprise Linux 9 `grafana-0:9.2.10-7.el9_3` [RHSA-2023:6420](https://access.redhat.com/errata/RHSA-2023:6420) ## Frequently Asked Questions Today we are releasing Grafana 9.2. Alongside with new features and other bug fixes, this release includes a Moderate severity security fix for CVE-2022-39201 We are also releasing security patches for Grafana 9.1.8 and Grafana 8.5.14 to fix these issues. Release 9.2, latest release, also containing security fix: - \[Download Grafana 9.2\](https://grafana.com/grafana/download/9.2) Release 9.1.8, only containing security fix: - \[Download Grafana 9.1.8\](https://grafana.com/grafana/download/9.1.8) Release 8.5.14, only containing security fix: - \[Download Grafana 8.5.14\](https://grafana.com/g O3 Security · Impact-Aware SCA ### Is CVE-2022-39201 in your dependencies? Find it across Go, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)