Description
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.
Published: 2026-10-15
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Modification of Loki Alerting Rules
Action: Immediate Patch
AI Analysis

Impact

Grafana’s data source proxy does not enforce role‑based access control on POST, PUT, and DELETE requests sent to the Loki rules API. Because the Loki rules are stored inside Loki rather than in Grafana, a user with only the Viewer role can create, modify, or delete alerting rules that affect every client that uses the same Loki data source. The vulnerability therefore allows an authenticated low‑privilege user to tamper with alert configurations, potentially suppressing legitimate alerts or generating false alarms, which compromises the integrity of monitoring and can lead to unnoticed incidents or deliberate sabotage.

Affected Systems

The flaw is present in both Grafana OSS and Grafana Enterprise. Any instance configured with a Loki data source that forwards write requests through Grafana’s proxy is affected. No specific Grafana version is listed; users should check the vendor advisory for the applicable releases. Loki itself is not vulnerable and does not need to be patched.

Risk and Exploitability

The CVSS base score is 7.1, indicating high severity. The EPSS score is less than 1%, suggesting that exploitation is currently unlikely. The vulnerability is not listed in the CISA KEV catalog. An attacker only needs a legitimate Viewer account and a configured Loki data source; no higher privileges were required. Once exploited, changes apply at the Loki level, affecting all users of that data source across the organization.

Generated by OpenCVE AI on October 16, 2026 at 21:08 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Grafana update that enforces role‑based access control on Loki write requests.
  • If an immediate upgrade is not possible, restrict Viewer role access to Loki data sources or block the Loki rules API via firewall or Loki configuration settings.
  • Monitor the Loki rules API for unexpected changes and isolate the Loki instance if unauthorized modifications are detected.

Generated by OpenCVE AI on October 16, 2026 at 21:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 21 Oct 2026 20:30:00 +0000

Type Values Removed Values Added
First Time appeared Grafana
Grafana grafana
Grafana grafana Enterprise
Vendors & Products Grafana
Grafana grafana
Grafana grafana Enterprise

Thu, 15 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Viewer role can create, modify and delete Loki alerting rules
Weaknesses CWE-284
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L'}


Subscriptions

Grafana Grafana Grafana Enterprise
cve-icon MITRE

Status: PUBLISHED

Assigner: GRAFANA

Published:

Updated: 2026-10-16T18:52:39.623Z

Reserved: 2026-05-27T12:38:34.129Z

Link: CVE-2026-9703

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-15T15:17:39.180

Modified: 2026-10-16T20:02:37.630

Link: CVE-2026-9703

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-21T20:15:05Z

Weaknesses