Technical impact
A Grafana installation that logs user authentication data can inadvertently write OAuth and OIDC access, refresh, and ID tokens to its server log files. The vulnerability is triggered when a token is not a valid JSON Web Token, when an ID token is missing, or is not a string. The logged tokens are written at debug level or higher, and the sensitive data is exposed as plain text. Attackers who can read Grafana server logs or the log store therefore have the opportunity to obtain authentication tokens for users who sign in via the Generic OAuth, Google, or GitLab connectors. The tokens are restricted to the scopes granted to the configured OAuth client, but the exposure still allows credential compromise, replay attacks, or unauthorized access to authenticated services.
Affected Systems
Grafana Enterprise and Grafana OSS are affected. No specific version ranges were provided in the advisory, so the risk applies to any release that has not applied the redaction fix. The issue is bounded by the scopes granted to the configured OAuth client, meaning the extent of the leakage depends on the permissions configured in Grafana for each provider.
Risk and Exploitability
The CVSS score of 6.0 indicates a medium impact, and the EPSS score is 0.00161 (<1%), indicating a low probability of exploitation. The flaw is not listed in the CISA KEV catalog. The attack vector is local or as part of an internal audit: any user who has read access to the Grafana server logs or the external log store can recover the credentials. Because the vulnerability requires only logged data to be available, it can be leveraged without network-level access, making it a significant internal exposure risk.