cve.bz

CVE-2026-79656 grafana

6.0 mediumEPSS 0.2%

Medium (6.0) in grafana. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.0 medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-79656 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79656?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79656?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-79656 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • grafana:grafana enterprise
  • grafana:grafana oss

Versions

From the CNA's record in the CVE List.

ProductAffected
Grafana OSSthrough 12.3.11
Grafana OSSfrom 12.4.0 before 12.4.11
Grafana OSSfrom 13.0.0 before 13.0.9
Grafana OSSfrom 13.1.0 before 13.1.6
Grafana OSSfrom 13.2.0 before 13.2.2
Grafana Enterprisethrough 12.3.11
Grafana Enterprisefrom 12.4.0 before 12.4.11
Grafana Enterprisefrom 13.0.0 before 13.0.9
Grafana Enterprisefrom 13.1.0 before 13.1.6
Grafana Enterprisefrom 13.2.0 before 13.2.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hathummingbird:1grafana12.40:12.4.13-0.5.hum1RHSA-2026:91292
Red Hathummingbird:1grafana13.10:13.1.8-0.5.hum1RHSA-2026:91181
Red Hathummingbird:1grafana13.20:13.2.4-0.4.hum1RHSA-2026:90990
openSUSETumbleweedgrafana12.4.11-1.1openSUSE-SU-2026:11920-1
Alpinev3.24grafana12.4.14-r0ALPINE-CVE-2026-79656

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is rated Moderate because it requires local access to Grafana server logs to exploit. While sensitive OAuth and OIDC tokens may be written to logs under specific SSO configurations, the vulnerability is not remotely exploitable, and the impact is limited by the scopes granted to the Grafana OAuth client, preventing direct account takeover.

Red Hat's mitigation

To mitigate this issue, restrict read access to Grafana server logs and any downstream log pipelines. Additionally, minimize the scopes granted to the Grafana OAuth client to limit the potential impact of leaked tokens. If your identity provider issues long-lived or non-expiring tokens, consider rotating the Grafana OAuth client secret and revoking issued tokens at the provider.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgrafana13-2-main-13.2.4-0.4.hum1Fixed 2026-10-27RHSA-2026:90990
Red Hat Hardened Imagesgrafana13-1-main-13.1.8-0.5.hum1Fixed 2026-10-27RHSA-2026:91181
Red Hat Hardened Imagesgrafana12-4-main-12.4.13-0.5.hum1Fixed 2026-10-27RHSA-2026:91292
Multicluster Global Hubmulticluster-globalhub/multicluster-globalhub-grafana-rhel9Fix deferred
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/acm-grafana-rhel9Fix deferred
Red Hat Ceph Storage 7rhceph/grafana-rhel9Fix deferred
Red Hat Ceph Storage 8rhceph/grafana-rhel9Fix deferred
Red Hat Ceph Storage 9rhceph/grafana-rhel10Fix deferred
Red Hat Enterprise Linux 10grafanaFix deferred
Red Hat Enterprise Linux 10rhel10/grafanaFix deferred
Red Hat Enterprise Linux 8grafanaFix deferred
Red Hat Enterprise Linux 9grafanaFix deferred
Red Hat Enterprise Linux 9rhel9/grafanaFix deferred
Red Hat Hardened Imageshi/grafanaNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-79656.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON