Grafana account takeover via OAuth vulnerability
CVE-2022-31107GHSA-mx47-6497-3fv2
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/grafana/grafana 9.0.3, 8.5.9, 8.4.10, 8.3.10), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- >= 8.4.0, < 8.4.10>= 8.5.0, < 8.5.9>= 9.0.0, < 9.0.3>= 5.3.0-beta1, < 8.3.10
- Fixed in
- 8.4.10, 9.0.3, 8.5.9, 8.3.10
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-mx47-6497-3fv2 lists affected ranges: Go github.com/grafana/grafana >=8.4.0 =8.5.0 =9.0.0 =5.3.0-beta1 <8.3.10
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.6 · 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 · score source
- EPSS
- CVE-2022-31107: 2.87% estimated exploitation activity in the next 30 days; percentile 86.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 - Release notes Release v.8.5.9, containing this security fix and other fixes: - Download Grafana 8.5.9 - Release notes Release v.8.4.10, containing this security fix and other fixes: - Download Grafana 8.4.10 - Release notes Release v.8.3.10, containing this security fix and other fixes: - Download Grafana 8.3.10 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-mx47-6497-3fv2
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2022-31107 Advisory: Grafana account takeover via OAuth vulnerability IDs: CVE-2022-31107, GHSA-mx47-6497-3fv2 Record: https://patchnext.com/advisories/cve-2022-31107 (revision 1, source checked 26 Oct 2026, 15:14 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/grafana/grafana 9.0.3, 8.5.9, 8.4.10, 8.3.10. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/grafana/grafana: affected >= 8.4.0, < 8.4.10; >= 8.5.0, < 8.5.9; >= 9.0.0, < 9.0.3; >= 5.3.0-beta1, < 8.3.10; fixed in 8.4.10, 9.0.3, 8.5.9, 8.3.10 ## Suggested inspection (read-only) - Go github.com/grafana/grafana: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/grafana/grafana. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-mx47-6497-3fv2 (GitHub-reviewed advisory GHSA-mx47-6497-3fv2 lists affected ranges: Go github.com/grafana/grafana >=8.4.0 =8.5.0 =9.0.0 =5.3.0-beta1 <8.3.10) Commands are suggestions: review each one before running it.
Loading voting…