CVE-2026-9703 — Viewer role can create, modify and delete Loki alerting rules
Grafana's data source proxy did not apply role-based access control to write requests forwarded to Loki data sources. A user holding only the Viewer role on an affected Grafana instance could send POST, PUT and DELETE requests through the proxy to the Loki rules API (/loki/api/v1/rules), allowing them to create, modify and delete Loki alerting rules. Because those rules are stored by Loki rather than by Grafana, the change took effect for every user of that Loki data source, not only for the Viewer who made the request. Exploitation requires an authenticated Viewer account on the Grafana instance and a configured Loki data source; no other privileges are needed. Both Grafana OSS and Grafana Enterprise are affected. The defect is in Grafana's data source proxy; Loki itself is not vulnerable and does not need to be patched.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Grafana Grafana Enterprise, Grafana Grafana OSS).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Grafana | Grafana Enterprise | ≥ 8.0.0 and ≤ 11.5.10≥ 11.6.0 and ≤ 11.6.16≥ 12.0.0 and ≤ 12.1.10≥ 12.2.0 and ≤ 12.2.10≥ 12.3.0 and ≤ 12.3.8≥ 12.4.0 and ≤ 12.4.5≥ 13.0.0 and ≤ 13.0.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Grafana | Grafana OSS | ≥ 12.3.0 and ≤ 12.3.8≥ 12.4.0 and ≤ 12.4.5≥ 8.0.0 and ≤ 12.3.0≥ 13.0.0 and ≤ 13.0.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.1 | High | 2.8 | 4.2 | security@grafana.com via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | — | — | GRAFANA via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L (score shown at the top: security@grafana.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Published → Received
- Record published
- Affected products added · grafana/grafana enterprise, grafana/grafana oss
- CVSS changed · 7.1
- Source status changed · → Published
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-93294 Azure Monitor data source resource proxy allows calls to arbitrary Azure Resource Manager APIs 1d
- Medium CVE-2026-95502 A Git server that Grafana's Git Sync (provisioning) is configured to use can exhaust Grafana's... 1d
- Medium CVE-2026-33374 The Prometheus rule conversion API endpoints in Grafana do not limit request body size, allowing... 1d
- Medium CVE-2026-15577 A user or service account with read-only access to Git Sync (provisioning) connections can modify... 1d
- High CVE-2026-76154 CVE-2026-76154 CVE Record 27d
- Medium CVE-2026-17033 CVE-2026-17033 CVE Record Aug 24, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-9703 is "Viewer role can create, modify and delete Loki alerting rules", rated High. It affects Grafana Enterprise (Grafana); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.