CVE-2026-79656: OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors
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.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker needs read access to Grafana server logs or to a centralized log store receiving those logs. The impact is limited to users who authenticate through the Generic OAuth, Google, or GitLab providers.
Under what conditions are tokens written to logs?
Tokens may be logged unredacted when an access token or ID token is not a valid JWT. At debug log level, exposure can also occur when the ID token is missing or is not a string.
What could an attacker obtain from exposed logs?
They can recover OAuth or OIDC access, refresh, and ID tokens for affected sign-ins. The usable access is bounded by the scopes granted to Grafana's configured OAuth client.