HighGHSA-mx47-6497-3fv2BIT-grafana-2022-31107CVE-2022-31107GO-2024-2852

Grafana account takeover via OAuth vulnerability

Published 14 May 2024 · Updated 10 Sept 2026

Is your project on an affected github.com/grafana/grafana?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=5.3.0-beta1 <8.3.10
Fixed in
8.3.10
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v8.3.10
Affected
>=8.4.0 <8.4.10
Fixed in
8.4.10
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v8.4.10
Affected
>=8.5.0 <8.5.9
Fixed in
8.5.9
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v8.5.9
Affected
>=9.0.0 <9.0.3
Fixed in
9.0.3
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v9.0.3

Details

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:

Release v.8.5.9, containing this security fix and other fixes:

Release v.8.4.10, containing this security fix and other fixes:

Release v.8.3.10, containing this security fix and other fixes:

Grafana account takeover via OAuth vulnerability (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 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 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 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 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.

Is GHSA-mx47-6497-3fv2 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/grafana/grafana, and gives you the command that fixes it.

More advisories for github.com/grafana/grafana

  • LowCVE-2026-21727Grafana legacy correlations allow cross-tenant disclosure and deletion in github.com/grafana/grafana · 7 Oct 2026
  • LowCVE-2026-42127Grafana: Pre-authentication denial of service in the public dashboard query handler in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-9029Grafana geomap panel's XYZ tile layer has a sanitize-then-interpolate ordering bug in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-42129Grafana Loki datasource plugin's callResource handler contains a path traversal vulnerability. in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-10601Grafana: Path traversal in the Tempo and Loki data source plugins in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-33381Grafana: Users can generate Service Account tokens after permissions removal in github.com/grafana/grafana · 25 Jun 2026
All 112 advisories for github.com/grafana/grafana

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.