CVE-2026-79656

OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors

Published Oct 28, 2026 CVSS 3.1 · 6 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Grafana update that addresses the CWE-256 vulnerability by ensuring OAuth and OIDC tokens are not logged in clear text
  • Configure Grafana to log at a minimal level for authentication flows, avoiding debug‑level logging of sensitive tokens
  • Restrict read access to the Grafana server logs or external log stores to privileged users only

Generated by OpenCVE AI on October 30, 2026 at 02:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Grafana
Grafana grafana
Grafana grafana Enterprise
Vendors & Products Grafana
Grafana grafana
Grafana grafana Enterprise
Type Values Removed Values Added
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.
Title OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors
Weaknesses CWE-532
References
Metrics cvssV3_1

{'score': 6, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-256

    Plaintext Storage of a Password

  • CWE-532

    Insertion of Sensitive Information into Log File

Sources

Status
PUBLISHED
Assigner
GRAFANA
Published
Updated
Nov 5, 2026, 4:56 PM
Reserved
Aug 25, 2026, 11:00 AM
Status
Awaiting Analysis
Published
Oct 28, 2026, 6:17 PM
Modified
Nov 5, 2026, 5:18 PM
Severity
Moderate
Public date
Oct 29, 2026, 1:02 PM