GPU VulnDB

Database/Control plane, storage & DevOps

Grafana: read-only Git Sync users can change a connection's configuration via its status subresource

CVSS 6.5CVE-2026-15577Control plane, storage & DevOpscurated

Impact

A user or service account holding only read access to a Git Sync provisioning connection can modify that connection's configuration through its status subresource, because authorization is checked on the main resource and not on the subresource. Git Sync is what defines where Grafana's dashboards and alert rules come from, so an actor who can repoint or reconfigure a connection can change what the observability layer displays and alerts on - the thing operators look at to decide whether a GPU fleet is healthy. Integrity only; no data disclosure is claimed. On Grafana 12.4 the affected API exists only when the experimental provisioning feature toggle is enabled, which limits this to instances that opted in.

Who can reach it

Any authenticated Grafana user or service account with read-only access to a Git Sync connection, over the network. No user interaction.

What to do

Upgrade to the fixed Grafana versions listed in the vendor advisory and restart the server. If you are on 12.4 and not using Git Sync, disabling the experimental provisioning feature toggle removes the affected API - that is a config change plus restart, no node work. After patching, review Git Sync connection configurations against what you expect, since changes made through this path would look like ordinary status updates.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.