Grafana account takeover via OAuth vulnerability
cve-program · CVE-2022-31107
PublishedGrafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
Read the publisher's advisoryeuvd · EUVD-2024-1698
PublishedGrafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
Read the publisher's advisorynvd · CVE-2022-31107
PublishedGrafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
Read the publisher's advisoryosv · GHSA-mx47-6497-3fv2
PublishedToday we are releasing Grafana 8.3.10, 8.4.10, 8.5.9 and 9.0.3. This patch release includes a HIGH severity security fix for an Oauth takeover vulnerability in Grafana. Release v.9.0.3, containing this security fix and other patches: - [Download Grafana 9.0.3](https://grafana.com/grafana/download/9.0.3) - [Release notes](https://grafana.com/docs/grafana/next/release-notes/release-notes-9-0-3/) Release v.8.5.9, containing this security fix and other fixes: - [Download Grafana 8.5.9](https://grafana.com/grafana/download/8.5.9) - [Release notes](https://grafana.com/docs/grafana/next/release-notes/release-notes-8-5-9/) Release v.8.4.10, containing this security fix and other fixes: - [Download Grafana 8.4.10](https://grafana.com/grafana/download/8.4.10) - [Release notes](https://grafana.com/docs/grafana/next/release-notes/release-notes-8-4-10/) Release v.8.3.10, containing this security fix and other fixes: - [Download Grafana 8.3.10](https://grafana.com/grafana/download/8.3.10) ## Grafana account takeover via OAuth vulnerability ([CVE-2022-31107](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31107)) ### Summary On June 27 the HTTPVoid team contacted Grafana Labs to disclose a Grafana account takeover via an OAuth vulnerability. We believe that this vulnerability is rated at CVSS 7.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L). ### Impact It is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP to take over an existing Grafana account under some conditions. ### Affected versions with HIGH severity All Grafana >=5.3 versions are affected by this vulnerability. ### Solutions and mitigations All installations after Grafana v5.3 should be upgraded as soon as possible. As a workaround it is possible to [disable any OAuth login](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/generic-oauth/) or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address. 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. ### Timeline Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC. 2022-06-27 19:00 - Research submission of vulnerability report 2022-06-27 20:53 - Issue triaged, confirmed positive, and internal incident raised 2022-06-28 08:42 - Fix PR submitted and reviewed 2022-06-28 20:58 - All Grafana Cloud hosted Grafana instances patched 2022-07-05 07:14 - Customers informed under embargo 2022-07-14 02:00 - Public release ### Acknowledgement We would like to thank the HTTPVoid team for responsibly disclosing the vulnerability. ### 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 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).
Read the publisher's advisoryosv · GO-2024-2852
PublishedGrafana account takeover via OAuth vulnerability in github.com/grafana/grafana. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/grafana/grafana from v5.3.0 before v8.3.10, from v8.4.0 before v8.4.10, from v8.5.0 before v8.5.9, from v9.0.0 before v9.0.3.
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2022-31107
PublishedGrafana account takeover via OAuth vulnerability
Grafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
- Source published
- 15 Jul 2022 12:30:14 UTC
- Source modified
- 28 Jan 2026 04:55:31 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
euvd · EUVD-2024-1698
PublishedGrafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP…
Grafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jul 15, 2022, 12:30:14 PM
dateUpdated: Jan 28, 2026, 4:55:31 AM
21 related source bulletins · separate from aliases
SUSE-SU-2023:2578-1: Security update for SUSE Manager Client Tools
CVE-2020-7753 · CVE-2021-3807 · CVE-2021-3918 · CVE-2021-43138 · CVE-2022-0155 · CVE-2022-27664 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-32149 · CVE-2022-35957 · CVE-2022-36062 · CVE-2022-41715 · CVE-2022-46146 · CVE-2023-1387 · CVE-2023-1410
RHSA-2022:5717: security update for grafana
CVE-2022-31107
SUSE-SU-2022:4428-1: Security update for grafana
CVE-2021-36222 · CVE-2021-3711 · CVE-2021-41174 · CVE-2021-41244 · CVE-2021-43798 · CVE-2021-43813 · CVE-2021-43815 · CVE-2022-29170 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-35957 · CVE-2022-36062
SUSE-SU-2024:0196-1: Security Beta update for SUSE Manager Client Tools and Salt
CVE-2020-7753 · CVE-2021-20178 · CVE-2021-20180 · CVE-2021-20191 · CVE-2021-20228 · CVE-2021-3447 · CVE-2021-3583 · CVE-2021-3620 · CVE-2021-36222 · CVE-2021-3711 · CVE-2021-3807 · CVE-2021-3918 · CVE-2021-41174 · CVE-2021-41244 · CVE-2021-43138 · CVE-2021-43798 · CVE-2021-43813 · CVE-2021-43815 · CVE-2022-0155 · CVE-2022-23552 · CVE-2022-27664 · CVE-2022-29170 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-31123 · CVE-2022-31130 · CVE-2022-32149 · CVE-2022-35957 · CVE-2022-36062 · CVE-2022-39201 · CVE-2022-39229 · CVE-2022-39306 · CVE-2022-39307 · CVE-2022-39324 · CVE-2022-41715 · CVE-2022-41723 · CVE-2022-46146 · CVE-2023-0507 · CVE-2023-0594 · CVE-2023-1387 · CVE-2023-1410 · CVE-2023-2183 · CVE-2023-2801 · CVE-2023-3128
RHSA-2023:3642: Red Hat Security Advisory: Red Hat Ceph Storage 6.1 Container security and bug fix update
CVE-2021-42581 · CVE-2022-1650 · CVE-2022-1705 · CVE-2022-2880 · CVE-2022-21680 · CVE-2022-21681 · CVE-2022-23498 · CVE-2022-24675 · CVE-2022-24785 · CVE-2022-26148 · CVE-2022-27664 · CVE-2022-28131 · CVE-2022-28327 · CVE-2022-29526 · CVE-2022-30629 · CVE-2022-30630 · CVE-2022-30631 · CVE-2022-30632 · CVE-2022-30633 · CVE-2022-30635 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-31123 · CVE-2022-31130 · CVE-2022-32148 · CVE-2022-32189 · CVE-2022-32190 · CVE-2022-35957 · CVE-2022-39201 · CVE-2022-39229 · CVE-2022-39306 · CVE-2022-39307 · CVE-2022-39324 · CVE-2022-41715 · CVE-2022-41912
SUSE-SU-2022:3747-1: Security update for SUSE Manager Client Tools
CVE-2022-21698 · CVE-2022-31097 · CVE-2022-31107
WID-SEC-W-2022-0696: Grafana: Mehrere Schwachstellen
CVE-2022-31097 · CVE-2022-31107
SUSE-SU-2022:3676-1: Security update for grafana
CVE-2021-36222 · CVE-2021-3711 · CVE-2021-41174 · CVE-2021-41244 · CVE-2021-43798 · CVE-2021-43815 · CVE-2022-21673 · CVE-2022-21702 · CVE-2022-21703 · CVE-2022-21713 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-35957 · CVE-2022-36062
RHSA-2022:5716: security update for grafana
CVE-2022-31107
SUSE-SU-2022:4439-1: Security update for SUSE Manager Client Tools
CVE-2021-36222 · CVE-2021-3711 · CVE-2021-41174 · CVE-2021-41244 · CVE-2021-43798 · CVE-2021-43813 · CVE-2021-43815 · CVE-2022-29170 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-35957 · CVE-2022-36062
RHSA-2022:5720: Red Hat Security Advisory: grafana security update
CVE-2022-31107
SUSE-SU-2022:3751-1: Security update for SUSE Manager Client Tools
CVE-2022-31097 · CVE-2022-31107
RHSA-2022:5719: Red Hat Security Advisory: grafana security update
CVE-2022-31107
RHSA-2022:5718: Red Hat Security Advisory: grafana security update
CVE-2022-31107
WID-SEC-W-2022-1582: GitLab: Mehrere Schwachstellen ermöglichen Cross-Site Scripting
CVE-2022-2882 · CVE-2022-2904 · CVE-2022-3018 · CVE-2022-3060 · CVE-2022-3066 · CVE-2022-3067 · CVE-2022-31107 · CVE-2022-3279 · CVE-2022-3283 · CVE-2022-3285 · CVE-2022-3286 · CVE-2022-3288 · CVE-2022-3291 · CVE-2022-3293 · CVE-2022-3325 · CVE-2022-3330 · CVE-2022-3351
SUSE-SU-2022:4437-1: Security update for SUSE Manager Client Tools
CVE-2021-36222 · CVE-2021-3711 · CVE-2021-41174 · CVE-2021-41244 · CVE-2021-43798 · CVE-2021-43813 · CVE-2021-43815 · CVE-2022-29170 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-35957 · CVE-2022-36062
openSUSE-SU-2024:12260-1: grafana-8.3.10-1.1 on GA media
CVE-2022-31097 · CVE-2022-31107
SUSE-SU-2022:3765-1: Security update for grafana
CVE-2022-21702 · CVE-2022-21703 · CVE-2022-21713 · CVE-2022-31097 · CVE-2022-31107
SUSE-SU-2023:2575-1: Security update for SUSE Manager Client Tools
CVE-2020-7753 · CVE-2021-3807 · CVE-2021-3918 · CVE-2021-43138 · CVE-2022-0155 · CVE-2022-27664 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-32149 · CVE-2022-35957 · CVE-2022-36062 · CVE-2023-1387 · CVE-2023-1410
SUSE-SU-2024:0191-1: Security Beta update for SUSE Manager Client Tools
CVE-2020-7753 · CVE-2021-36222 · CVE-2021-3711 · CVE-2021-3807 · CVE-2021-3918 · CVE-2021-39226 · CVE-2021-41174 · CVE-2021-41244 · CVE-2021-43138 · CVE-2021-43798 · CVE-2021-43813 · CVE-2021-43815 · CVE-2022-0155 · CVE-2022-21673 · CVE-2022-21698 · CVE-2022-21702 · CVE-2022-21703 · CVE-2022-21713 · CVE-2022-23552 · CVE-2022-27191 · CVE-2022-27664 · CVE-2022-29170 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-31123 · CVE-2022-31130 · CVE-2022-32149 · CVE-2022-35957 · CVE-2022-36062 · CVE-2022-39201 · CVE-2022-39229 · CVE-2022-39306 · CVE-2022-39307 · CVE-2022-39324 · CVE-2022-41715 · CVE-2022-41723 · CVE-2022-46146 · CVE-2023-0507 · CVE-2023-0594 · CVE-2023-1387 · CVE-2023-1410 · CVE-2023-2183 · CVE-2023-2801 · CVE-2023-3128 · CVE-2023-40577
SUSE-SU-2023:2579-1: Security update for SUSE Manager Client Tools
CVE-2020-7753 · CVE-2021-3807 · CVE-2021-3918 · CVE-2021-43138 · CVE-2022-0155 · CVE-2022-27191 · CVE-2022-27664 · CVE-2022-31097 · CVE-2022-31107 · CVE-2022-32149 · CVE-2022-35957 · CVE-2022-36062 · CVE-2022-41715 · CVE-2022-46146 · CVE-2023-1387 · CVE-2023-1410
- Source published
- Jul 15, 2022, 12:30:14 PM (timezone not stated)
- Source modified
- Jan 28, 2026, 4:55:31 AM (timezone not stated)
- Saved here
- 18 Nov 2026 09:52:48 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
nvd · CVE-2022-31107
PublishedGrafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP…
Grafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-863
Original publisher date fields
published: 2022-07-15T13:15:08.397
lastModified: 2026-06-17T04:44:48.813
2 source CPE criteria · context only
- cpe:2.3:a:grafana:grafana:*:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:e-series_performance_analyzer:-:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 15 Jul 2022 13:15:08 UTC
- Source modified
- 17 Jun 2026 04:44:48 UTC
- Saved here
- 24 Oct 2026 20:17:25 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv · GHSA-mx47-6497-3fv2
PublishedGrafana account takeover via OAuth vulnerability
Today we are releasing Grafana 8.3.10, 8.4.10, 8.5.9 and 9.0.3. This patch release includes a HIGH severity security fix for an Oauth takeover vulnerability in Grafana. Release v.9.0.3, containing this security fix and other patches: - [Download Grafana 9.0.3](https://grafana.com/grafana/download/9.0.3) - [Release notes](https://grafana.com/docs/grafana/next/release-notes/release-notes-9-0-3/) Release v.8.5.9, containing this security fix and other fixes: - [Download Grafana 8.5.9](https://grafana.com/grafana/download/8.5.9) - [Release notes](https://grafana.com/docs/grafana/next/release-notes/release-notes-8-5-9/) Release v.8.4.10, containing this security fix and other fixes: - [Download Grafana 8.4.10](https://grafana.com/grafana/download/8.4.10) - [Release notes](https://grafana.com/docs/grafana/next/release-notes/release-notes-8-4-10/) Release v.8.3.10, containing this security fix and other fixes: - [Download Grafana 8.3.10](https://grafana.com/grafana/download/8.3.10) ## Grafana account takeover via OAuth vulnerability ([CVE-2022-31107](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31107)) ### Summary On June 27 the HTTPVoid team contacted Grafana Labs to disclose a Grafana account takeover via an OAuth vulnerability. We believe that this vulnerability is rated at CVSS 7.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L). ### Impact It is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP to take over an existing Grafana account under some conditions. ### Affected versions with HIGH severity All Grafana >=5.3 versions are affected by this vulnerability. ### Solutions and mitigations All installations after Grafana v5.3 should be upgraded as soon as possible. As a workaround it is possible to [disable any OAuth login](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/generic-oauth/) or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address. 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. ### Timeline Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC. 2022-06-27 19:00 - Research submission of vulnerability report 2022-06-27 20:53 - Issue triaged, confirmed positive, and internal incident raised 2022-06-28 08:42 - Fix PR submitted and reviewed 2022-06-28 20:58 - All Grafana Cloud hosted Grafana instances patched 2022-07-05 07:14 - Customers informed under embargo 2022-07-14 02:00 - Public release ### Acknowledgement We would like to thank the HTTPVoid team for responsibly disclosing the vulnerability. ### 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 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).
- Source published
- 14 May 2024 22:22:35 UTC
- Source modified
- 10 Sep 2026 03:49:18 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
CVSS_V4 · CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Publisher rating · HIGH
osv · GO-2024-2852
PublishedGrafana account takeover via OAuth vulnerability in github.com/grafana/grafana
Grafana account takeover via OAuth vulnerability in github.com/grafana/grafana. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/grafana/grafana from v5.3.0 before v8.3.10, from v8.4.0 before v8.4.10, from v8.5.0 before v8.5.9, from v9.0.0 before v9.0.3.
- Source published
- 5 Jun 2024 15:10:42 UTC
- Source modified
- 4 Feb 2026 02:33:46 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.