cve.bz

CVE-2026-9703 grafana: Improper Access Control

7.1 highEPSS 0.2%

High (7.1) in grafana. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-9703 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9703?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9703?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9703 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • grafana:grafana enterprise
  • grafana:grafana oss

Versions

From the CNA's record in the CVE List.

ProductAffected
Grafana Enterprisefrom 8.0.0 through 11.5.10
Grafana Enterprisefrom 11.6.0 through 11.6.16
Grafana Enterprisefrom 12.0.0 through 12.1.10
Grafana Enterprisefrom 12.2.0 through 12.2.10
Grafana Enterprisefrom 12.3.0 through 12.3.8
Grafana Enterprisefrom 12.4.0 through 12.4.5
Grafana Enterprisefrom 13.0.0 through 13.0.3
Grafana OSSfrom 12.3.0 through 12.3.8
Grafana OSSfrom 12.4.0 through 12.4.5
Grafana OSSfrom 8.0.0 through 12.3.0
Grafana OSSfrom 13.0.0 through 13.0.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweeddistribution3.1.2-3.1openSUSE-SU-2026:12283-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON