EUVD-2026-89774
GHSA-46f2-3vm3-9h7j
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged Grafana user
-
DeliveryCall alert rules API list endpoint with folder filter
-
ExploitFolder read restriction dropped/bypassed
-
ExecutionReceive alert rules from unauthorized folders
-
ImpactHarvest rule configuration data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated Grafana account (any low-privilege user) and use of the alert rules API list endpoint. Two triggering conditions apply: (1) when the set of folders the user is permitted to read is empty, the folder restriction is dropped entirely and all alert rules in the organization are returned; and (2) from Grafana 13.1.0 onward, any user can trigger cross-folder disclosure by supplying a folder filter to the endpoint. Limiting factors: authentication is mandatory (PR:L), the disclosure is confidentiality-only, and the exposed content is limited to alert rule configuration - data source credentials are not exposed. |
| Impact | This is a genuine but low-severity information-disclosure issue, not a top-tier priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3) correctly reflects the impact: network-reachable, low attack complexity, but requiring an authenticated low-privilege account and yielding only limited confidentiality loss (C:L) with no integrity or availability impact. No EPSS score, KEV listing, or public POC was provided in the intelligence set, so there is no signal of active exploitation or automated weaponization. The exposed data is alert-rule configuration only - the advisory explicitly states data source credentials are NOT exposed - which caps the real-world harm. The one aggravating factor is that from Grafana 13.1.0 the empty-folder-set edge case was generalized so any user can trigger cross-folder disclosure via a folder filter, widening the affected population, but this still requires a valid authenticated session. Net: real but low-priority; patch on normal cadence rather than emergency. |
| Exploit ScenarioDerived | A low-privileged authenticated Grafana user calls the alert rules API list endpoint (optionally supplying a folder filter) and receives alert rule configurations from folders they have no read permission for, including - in the empty-readable-folders case - every alert rule in the organization. No public exploit code was identified, but the technique is a trivial API call requiring no special tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
An authenticated, low-privilege Grafana user can read alert rule configurations from folders they are not authorized to view through the alert rules API list endpoint, because the folder-based authorization filter is dropped when the caller's set of readable folders is empty - causing the endpoint to return every alert rule in the organization. Starting with Grafana 13.1.0, any user can also trigger cross-folder disclosure by simply supplying a folder filter to that same endpoint. The impact is confidentiality-only and limited to rule configuration metadata (data source credentials are not exposed); the vendor (security@grafana.com) is the reporting source, and no public exploit code has been identified at time of analysis.
RemediationAI
Apply the fixed Grafana release identified in the vendor advisory at https://grafana.com/security/security-advisories/cve-2026-13719; the input data does not specify an exact patched version number, so verify the target version against that advisory rather than assuming one, and upgrade both the 13.1.x line and any older supported branches the advisory lists. If upgrading cannot be performed immediately, use compensating controls that specifically defeat the two trigger paths: ensure no user account, service account, or team is left with an empty readable-folder set for alerting (grant at least one folder-level read permission, which forces the restriction to be applied) - the trade-off is additional RBAC bookkeeping and periodic audits, since new accounts and provisioned service tokens can silently reintroduce the empty-set condition; and, where alert-rule administration does not need to be user-facing, block or restrict access to the alert rules API list endpoint at the reverse proxy for non-administrative roles, accepting that this also breaks the Grafana alerting UI, provisioning/API-driven rule management, and CI/CD pipelines that read rules through the same endpoint. Until a fix is in place, treat alert rule configuration as potentially organization-visible and avoid embedding sensitive operational details (contact points, escalation naming, routing structure) in rule metadata, and review server and audit logs for list requests carrying folder filters as a detection signal for the 13.1.0+ path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), realized as a fail-open authorization bug in Grafana's unified alerting layer rather than a flaw in the alerting engine itself. Grafana grants read access to alert rules through folder-level permissions; the alert rules API list handler is expected to translate the caller's folder permissions into a query restriction that limits returned rules to readable folders. When that permission set evaluates to empty (i.e., the user has no readable folders), the handler omits the restriction entirely instead of returning an empty result, so the query falls through to an organization-wide listing. Grafana 13.1.0 introduced behavior where a client-supplied folder filter parameter on the list endpoint is honored without being reconciled against the caller's permissions, giving any authenticated user a second, simpler path to the same disclosure. CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N confirms the attack is network-reachable and low-complexity but requires valid credentials (PR:L) and yields only a limited confidentiality impact (C:L) with no integrity or availability effect. CPE strings were not supplied in the input data; the relevant attack surface is the Grafana alert rules list API exposed by the Grafana server.
Know when Grafana gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Network API reachable with low complexity but needs an authenticated low-privilege account (PR:L); limited confidentiality loss of rule config only (C:L), no integrity or availability impact.
Primary rating from Vendor (grafana).
CVSS VectorVendor: grafana
Lifecycle Timeline
2DescriptionCVE.org
An authenticated user can list alert rules stored in folders they are not allowed to read through the alert rules API list endpoint. When the set of folders the user may read was empty, the folder restriction was dropped and every alert rule in the organization was returned. From Grafana 13.1.0, any user can trigger this with a folder filter. The exposed data is rule configuration; data source credentials are not exposed.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The SQL Expressions experimental feature of Grafana allows for the evaluation of `duckdb` queries containing user input.
The `Release PR Merged` workflow in the github repo taosdata/grafanaplugin is subject to a command injection vulnerabili
An issue was discovered in Grafana through 7.3.4, when integrated with Zabbix. Rated critical severity (CVSS 9.8), this
A signature verification vulnerability exists in crewjam/saml. Rated critical severity (CVSS 9.8), this vulnerability is
Grafana 2.x, 3.x, and 4.x before 4.6.4 and 5.x before 5.2.3 allows authentication bypass because an attacker can generat
Authentication bypass in Grafana OnCall through 1.16.11 lets unauthenticated remote attackers mint a valid PluginAuthTok
Insertion of sensitive information in the centralized (Grafana) logging system in ProLion CryptoSpike 3.0.15P2 allows re
A cross-site scripting (XSS) vulnerability exists in Grafana caused by combining a client path traversal and open redire
The avatar feature in Grafana 3.0.1 through 7.0.1 has an SSRF Incorrect Access Control issue. Rated high severity (CVSS
Grafana is an open-source platform for monitoring and observability. Rated high severity (CVSS 7.5), this vulnerability
Grafana 8.4.3 allows unauthenticated access via (for example) a /dashboard/snapshot/*?orgId=0 URI. Rated high severity (
Grafana 8.4.3 allows reading files via (for example) a /dashboard/snapshot/%7B%7Bconstructor.constructor'/.. Rated high
Exploit-DB