A user with read access to Grafana's server logs, or to a log store they are shipped to, can recover the OAuth and
Source GCVE Database
Not known to be exploited · CVSS 6.0 Medium · fixed in 13.2.2 : update Grafana OSS when convenient.
Data as of 28 Oct 2026, 19:29 UTC
- Patch
- Available – fixed in 13.2.2, 13.1.6, 13.0.9 +1
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Grafana to 13.2.2, 13.1.6, 13.0.9 or 12.4.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GrafanaGrafana OSS | Affected
| Fixed in
|
| GrafanaGrafana Enterprise | Affected
| Fixed in
|
AI-suggested
Since this vulnerability requires read access to server logs or log storage, restricting access to these logs and avoiding debug-level logging in production environments can mitigate exposure. Monitor vendor advisories for any forthcoming patches or updates.
Description
A vulnerability in Grafana allows users with read access to server logs or log stores to recover OAuth and OIDC tokens for users authenticated via Generic OAuth, Google, or GitLab providers. This occurs because Grafana logs these tokens unredacted under certain conditions, such as invalid JWT tokens or missing ID tokens at debug level. The exposure is limited to the scopes granted to the OAuth client.