Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

Exploitation and risk

Source status

CISA 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-39229

Published

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.

Source published
13 Oct 2022 00:00:00 UTC
Source modified
23 Apr 2025 16:50:38 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 · 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

euvd · EUVD-2024-1627

Published

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.

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: Oct 13, 2022, 12:00:00 AM

dateUpdated: Apr 23, 2025, 4:50:38 PM

10 related source bulletins · separate from aliases

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-2023:0362-1: Security update for grafana

CVE-2022-31123 · CVE-2022-31130 · CVE-2022-39201 · CVE-2022-39229 · CVE-2022-39306 · CVE-2022-39307

SUSE-SU-2023:0352-1: Security update for SUSE Manager Client Tools

CVE-2022-31123 · CVE-2022-31130 · CVE-2022-39201 · CVE-2022-39229 · CVE-2022-39306 · CVE-2022-39307

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

WID-SEC-W-2022-1702: Grafana: Mehrere Schwachstellen

CVE-2022-31123 · CVE-2022-31130 · CVE-2022-39201 · CVE-2022-39229

RHSA-2023:2784: Red Hat Security Advisory: grafana security update

CVE-2022-2880 · CVE-2022-27664 · CVE-2022-39229 · CVE-2022-41715

RHSA-2023:2167: Red Hat Security Advisory: grafana security and enhancement update

CVE-2022-2880 · CVE-2022-27664 · CVE-2022-35957 · CVE-2022-39229 · CVE-2022-41715

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:0353-1: Security update for SUSE Manager Client Tools

CVE-2022-31123 · CVE-2022-31130 · CVE-2022-39201 · CVE-2022-39229 · CVE-2022-39306 · CVE-2022-39307

openSUSE-SU-2024:12508-1: grafana-8.5.14-1.1 on GA media

CVE-2022-31123 · CVE-2022-31130 · CVE-2022-39201 · CVE-2022-39229

Source published
Oct 13, 2022, 12:00:00 AM (timezone not stated)
Source modified
Apr 23, 2025, 4:50:38 PM (timezone not stated)
Saved here
16 Nov 2026 02:43:59 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 · 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

nvd · CVE-2022-39229

Published

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.

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-287

Original publisher date fields

published: 2022-10-13T23:15:10.937

lastModified: 2026-06-17T04:57:57.520

1 source CPE criteria · context only
  • cpe:2.3:a:grafana:grafana:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
13 Oct 2022 23:15:10 UTC
Source modified
17 Jun 2026 04:57:57 UTC
Saved here
24 Oct 2026 20:17:36 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 · 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

CVSS 3.1 · [email protected] · Primary · 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

osv · GHSA-gj7m-853r-289r

Published

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](https://grafana.com/grafana/download/9.2) Release 9.1.8, only containing security fix: - [Download Grafana 9.1.8](https://grafana.com/grafana/download/9.1.8) Release 8.5.14, only containing security fix: - [Download Grafana 8.5.14](https://grafana.com/grafana/download/8.5.14) 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 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 in Grafana basic authentication, related to the usage of username and email address. In Grafana, a 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. In addition, a user can have an email address as a username and Grafana login allows users to sign in with either username or email address. This creates an unusual behavior, where _user_1_ can register with one email address and _user_2_ can register their username as _user_1_’s email address. As a result, _user_1_ would be prevented to sign in Grafana, since _user_1_ password won’t match with _users_2_ email address. The CVSS score for this vulnerability is 4.3 Moderate (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L). ### Impacted versions All installations for Grafana versions <=9.x, <=8.x ### Solutions and mitigations To fully address CVE-2022-39229 please upgrade your Grafana instances. Appropriate patches have been applied to [Grafana Cloud](https://grafana.com/cloud). ## 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:29:38 UTC
Source modified
10 Sep 2026 03:50:00 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:L/PR:L/UI:N/S:U/C:N/I:N/A:L

CVSS_V4 · 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

Publisher rating · MODERATE

osv · GO-2024-2848

Published

Grafana when using email as a username can block other users from signing in 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 before v8.5.14, from v9.0.0 before v9.1.8.

Source published
5 Jun 2024 15:10:42 UTC
Source modified
4 Feb 2026 04:03:33 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 22:31 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current