OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors
Impact
Grafana OSS and Enterprise versions up to 12.3.11, 12.4.10, 13.0.8, 13.1.5, and 13.2.1 write OAuth and OIDC tokens to server logs, allowing users with read access to recover tokens. The exposure is bounded by the scopes granted to the configured OAuth client. An attacker needs read access to the server logs.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Grafana · GRAFANA
Grafana OSS
5 ranges
Grafana · GRAFANA
Grafana OSS
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → through 12.3.11
semver versions
12.4.0 → before 12.4.11
semver versions
13.0.0 → before 13.0.9
semver versions
13.1.0 → before 13.1.6
semver versions
13.2.0 → before 13.2.2
semver versions
Other versions: unaffected
Grafana · GRAFANA
Grafana Enterprise
5 ranges
Grafana · GRAFANA
Grafana Enterprise
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → through 12.3.11
semver versions
12.4.0 → before 12.4.11
semver versions
13.0.0 → before 13.0.9
semver versions
13.1.0 → before 13.1.6
semver versions
13.2.0 → before 13.2.2
semver versions
Other versions: unaffected
Original source 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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-79656View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.