Grafana: OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors
Affects grafanaSource GCVE Database
Not known to be exploited · CVSS 6.0 Medium · fixed in 13.2.2 : update grafana when convenient.
Data as of 17 Nov 2026, 16:04 UTC
Thin evidence
One scorer or none| CNA (GRAFANA) | CVSS 3.1 | 6.0 |
|---|
- 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
Weaponized: 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 16 Nov 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 |
|---|---|---|
Bitnamigrafanapkg:bitnami/grafanaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
A user with read access to Grafana's server logs, or to a log store they are shipped to, can recover the OAuth and OIDC access, refresh and ID tokens of users who sign in through the Generic OAuth, Google or GitLab providers. Grafana writes these tokens to its logs unredacted when an access or ID token is not a valid JWT, when the ID token is missing (at debug level) or is not a string (exposure of sensitive information in log files). The exposure is bounded by the scopes granted to the configured OAuth client.