# CVE-2022-39229: Grafana users with email as a username can block other users from signing in

> An attacker can block legitimate users from signing in by registering their email address as a username, causing a denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-grafana-2022-39229, GHSA-gj7m-853r-289r, GO-2024-2848, MINI-4434-x9wp-qf3v, MINI-733g-vrm8-5ch7, MINI-74xc-jfc6-8rfm, MINI-7wxf-4pvp-5f34, MINI-cqqr-737g-5cfm, MINI-fr2p-7q25-7pj2, MINI-fv37-gfcx-mh5f, MINI-g694-h9mq-xgjx, MINI-g8rj-mj24-ppj9, MINI-gfhg-m88g-5vw6, MINI-hx3j-939q-65hh, MINI-pqg3-gxxv-qh4j, MINI-r4cr-83gm-j987, MINI-r6pw-4qpx-9378, MINI-r7jm-4xf7-cw8x, MINI-w4v9-h425-6jh7, MINI-xw62-3p79-j4v7, OESA-2024-2260, UBUNTU-CVE-2022-39229

## What is CVE-2022-39229?

CVE-2022-39229 is a medium-severity authentication bypass vulnerability in Grafana Grafana, published on 13 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grafana is an open source data visualization platform for metrics, logs, and traces. Versions prior to 9.1.8 and 8.5.14 allow one user to block another user's login attempt by registering someone else'e email address as a username. A Grafana user’s username and email address are unique fields, that means no other user can have the same username or email address as another user. A user can have an email address as a username. However, the login system allows users to log in with either username or email address. Since Grafana allows a user to log in with either their username or email address, this creates an usual behavior where `user_1` can register with one email address and `user_2` can register their username as `user_1`’s email address. This prevents `user_1` logging into the application since `user_1`'s password won’t match with `user_2`'s email address. Versions 9.1.8 and 8.5.14 contain a patch. There are no workarounds for this issue.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-39229?

6 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | All versions | None |
| `github.com/grafana/grafana` | Go | All versions | 8.5.14 |
| `github.com/grafana/grafana` | Go | All versions | 8.5.14 |
| `github.com/grafana/grafana` | Go | From 9.0.0 | 9.1.8 |
| `github.com/grafana/grafana` | Go | From 9.0.0 | 9.1.8 |
| `grafana` | Bitnami | All versions | 8.5.14, 9.1.8 |

Products: Grafana Grafana.

## How do I fix CVE-2022-39229?

Upgrade github.com/grafana/grafana to a fixed version for your release line: 8.5.14 or 9.1.8.

## Is CVE-2022-39229 being exploited?

There is no known exploitation of CVE-2022-39229 in the wild and no public exploit code.

## Other vulnerabilities in Grafana Grafana

- [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild)
- [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0)
- [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8)
- [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39229 and fix it if it is affected.

What it is: CVE-2022-39229 is a medium-severity authentication bypass vulnerability in Grafana Grafana, published on 13 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39229 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected all versions; no fix listed
- github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.14
- github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.14
- github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.1.8
- github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.1.8
- grafana (Bitnami): affected all versions; fixed in 8.5.14, 9.1.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39229/ (Markdown: https://insights.sbomify.com/CVE-2022-39229/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39229
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39229
- OSV: https://osv.dev/vulnerability/CVE-2022-39229

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39229/
Summaries are generated and may contain mistakes; the official description above is the record.