# CVE-2026-79656: OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors


- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-jgwg-2rm4-8mgf

## What is CVE-2026-79656?

CVE-2026-79656 is a medium-severity vulnerability in Grafana Enterprise, published on 28 Oct 2026. 

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-79656?


## How do I fix CVE-2026-79656?

Upgrade to a fixed version.

## Is CVE-2026-79656 being exploited?

There is no known exploitation of CVE-2026-79656 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-79656 and fix it if it is affected.

What it is: CVE-2026-79656 is a medium-severity vulnerability in Grafana Enterprise, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-79656 in the wild and no public exploit code.

Affected product: Grafana Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-79656/ (Markdown: https://insights.sbomify.com/CVE-2026-79656/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-79656
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-79656
- OSV: https://osv.dev/vulnerability/CVE-2026-79656

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-79656/
Summaries are generated and may contain mistakes; the official description above is the record.