Grafana when using email as a username can block other users from signing in

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2022-39229: 1.14% estimated exploitation activity in the next 30 days; percentile 66.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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-39229 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 Release 9.1.8, only containing security fix: - Download Grafana 9.1.8 Release 8.5.14, only containing security fix: - Download Grafana 8.5.14 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 and Azure's Grafana as a service offering. Improper authentication - CVE-2022-39229 Summary On September 7 as a result of an internal security audit we have discovered a security vulnerability…

Published by the source

14 May 2024, 22:29 UTC

Last modified by the source

7 Aug 2024, 05:01 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gj7m-853r-289r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39229

Advisory: Grafana when using email as a username can block other users from signing in
IDs: CVE-2022-39229, GHSA-gj7m-853r-289r
Record: https://patchnext.com/advisories/cve-2022-39229 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
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.1.8, 8.5.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/grafana: affected < 8.5.14; >= 9.0.0, < 9.1.8; fixed in 9.1.8, 8.5.14

## 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-gj7m-853r-289r (GitHub-reviewed advisory GHSA-gj7m-853r-289r lists affected ranges: Go github.com/grafana/grafana >=0 =9.0.0 <9.1.8)

Commands are suggestions: review each one before running it.