| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 1.94- |
Summary
A vulnerability, which was classified as problematic, has been found in Grafana OSS and Enterprise up to 12.3.11/12.4.10/13.0.8/13.1.5/13.2.1. Affected by this issue is some unknown functionality. Performing a manipulation results in log file. This vulnerability is identified as CVE-2026-79656. The attack is only possible with local access. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Grafana OSS and Enterprise up to 12.3.11/12.4.10/13.0.8/13.1.5/13.2.1. This affects an unknown functionality. The manipulation with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on integrity. The summary by CVE is:
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.
The advisory is shared at grafana.com. This vulnerability is uniquely identified as CVE-2026-79656 since 08/25/2026. The exploitability is told to be easy. An attack has to be approached locally. The exploitation needs additional levels of successful authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 12.4.11, 13.0.9, 13.1.6 or 13.2.2 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 12.3.0
- 12.3.1
- 12.3.2
- 12.3.3
- 12.3.4
- 12.3.5
- 12.3.6
- 12.3.7
- 12.3.8
- 12.3.9
- 12.3.10
- 12.3.11
- 12.4.0
- 12.4.1
- 12.4.2
- 12.4.3
- 12.4.4
- 12.4.5
- 12.4.6
- 12.4.7
- 12.4.8
- 12.4.9
- 12.4.10
- 13.0.0
- 13.0.1
- 13.0.2
- 13.0.3
- 13.0.4
- 13.0.5
- 13.0.6
- 13.0.7
- 13.0.8
- 13.1.0
- 13.1.1
- 13.1.2
- 13.1.3
- 13.1.4
- 13.1.5
- 13.2.0
- 13.2.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.1
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.0
CNA Vector (GRAFANA): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OSS/Enterprise 12.4.11/13.0.9/13.1.6/13.2.2
Timeline
08/25/2026 CVE reserved10/28/2026 Advisory disclosed
10/28/2026 VulDB entry created
10/28/2026 VulDB entry last update
Sources
Advisory: grafana.comStatus: Confirmed
CNA: GRAFANA
CVE: CVE-2026-79656 (🔒)
GCVE (CVE): GCVE-0-2026-79656
GCVE (VulDB): GCVE-100-428121
Entry
Created: 10/28/2026 18:48Changes: 10/28/2026 18:48 (62)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.