# CVE-2026-79656: Grafana sensitive information disclosure in OAuth/OIDC token logging

Source: https://junglewise.ai/threats/cve-2026-79656-a-user-with-read-access-to-grafana-s-server-logs-or-to-a-log  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-28. Updated: 2026-10-28  
License: CC BY 4.0 with a link back

CVE-2026-79656 · Severity: medium · CVSS 6 · Published 2026-10-28

Grafana, an observability platform used to monitor systems and applications, logs OAuth and OIDC tokens unredacted in certain error conditions. An attacker with read access to Grafana's server logs or centralized log storage can extract these tokens to impersonate users who authenticate via Google, GitLab, or Generic OAuth providers. The exposure is limited by the permissions granted to the OAuth application, but could still enable unauthorized access to integrated systems.

Technologies: [Grafana](https://junglewise.ai/threats/technologies/grafana-grafana). Vendors: [Grafana](https://junglewise.ai/threats/vendors/grafana).

## Quick answers

**Is CVE-2026-79656 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-79656 being exploited in the wild.

**How severe is CVE-2026-79656?** Medium severity, with a CVSS score of 6, published 28 October 2026.

**Which products and versions are affected?** Grafana Grafana.

**Is there a fix for CVE-2026-79656?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-79656 attacked?** It is attacked with local access or over the network.

**Am I affected by CVE-2026-79656?** Check whether you run Grafana. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

Grafana writes OAuth and OIDC access, refresh, and ID tokens to its logs unredacted when an access or ID token fails JWT validation, when the ID token is missing (at debug log level), or when the ID token is not a string. An attacker with read access to Grafana's logs or log aggregation systems can extract these tokens to authenticate as affected users. The vulnerability affects Generic OAuth, Google, and GitLab OAuth providers.

## Affected products

- Grafana Grafana

## Timeline

- 2026-10-28: disclosed

## References

- [https://grafana.com/security/security-advisories/cve-2026-79656](https://grafana.com/security/security-advisories/cve-2026-79656)

## Related threats

- [Grafana Elasticsearch data source denial of service via time range](https://junglewise.ai/threats/cve-2026-81843-grafana-is-an-open-source-platform-for-monitoring-and)
- [Grafana Elasticsearch data source improper authorization in resource proxy](https://junglewise.ai/threats/cve-2026-106475-the-elasticsearch-data-source-resource-proxy-forwards-the)
- [Grafana Prometheus data source path traversal](https://junglewise.ai/threats/cve-2026-106472-grafana-s-prometheus-data-source-passes-the-resource-path)
- [Grafana authorization bypass in team preferences endpoint](https://junglewise.ai/threats/cve-2026-82014-any-authenticated-user-including-a-viewer-could-change-the)
- [Grafana authorization bypass in Git Sync provisioning API](https://junglewise.ai/threats/cve-2026-13721-a-user-with-edit-access-to-one-folder-could-modify-move-or-delete)