Skip to content
Fencer Intel
high 7.1

CVE-2026-9703 json

Viewer role can create, modify and delete Loki alerting rules

published 27d ago modified 20d ago also BIT-grafana-2026-9703 , EUVD-2026-102073

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami grafana 12.3.9, 12.4.6, 13.0.4
  • grafana grafana_enterprise 12.3.9, 12.4.6, 13.0.4
  • grafana grafana 12.3.9, 12.4.6, 13.0.4
  • distribution openSUSE Tumbleweed 3.1.2-3.1

opensuse advisories openSUSE-SU-2026:12283-1

Is CVE-2026-9703 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-9703 updated cvss 7.1

grafana: Grafana: Viewer role can create, modify and delete Loki alerting rules

  • Red Hat Multicluster Global Hub multicluster-globalhub/multicluster-globalhub-grafana-rhel9 Red Hat Multicluster Global Hub 5 multicluster-globalhub/multicluster-globalhub-grafana-rhel9 Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/acm-grafana-rhel9 Red Hat Ceph Storage 5 rhceph/rhceph-5-dashboard-rhel8 Red Hat Ceph Storage 6 rhceph/rhceph-6-dashboard-rhel9 Red Hat Ceph Storage 7 rhceph/grafana-rhel9
    +4 more products
    Red Hat Ceph Storage 9 rhceph/grafana-rhel10 Red Hat Enterprise Linux 8 grafana, grafana-loki, grafana-mssql, grafana-mysql, grafana-selinux, grafana-graphite, +9 more Red Hat Enterprise Linux 9 grafana, rhel9/grafana, grafana-selinux, grafana 12.4.3-5.el10 Red Hat Enterprise Linux 10 rhel10/grafana, grafana 12.4.3-5.el10
    affected: workaround, no fix available “There is no supported configuration workaround. After upgrading, review Loki alerting rules for unexpected creations, modifications, or deletions.”
  • Red Hat Ceph Storage 8 rhceph/grafana-rhel9 Red Hat Hardened Images hi/grafana, grafana12.4 12.4.6-0.1.hum1, grafana13.1 13.1.1-0.1.hum1, grafana13.2 13.2.4-0.7.hum1
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
26d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
OSV 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Affected packages

ecosystem package affected fixed in
bitnami grafana
>=8.0.0, <12.3.9
>=12.4.0, <12.4.6
>=13.0.0, <13.0.4
12.3.9
12.4.6
13.0.4

Affected products

  • Grafana Grafana Enterprise
  • Grafana Grafana OSS

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.