GPU VulnDB

Database/Control plane, storage & DevOps

Grafana: folder-admin check ignores the folder, exposing deleted dashboards from other folders

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

Impact

Grafana's RBAC service did not take the requested folder into account when deciding whether a user is a folder administrator for listings of deleted dashboards. A user who holds dashboard permission-management rights on any one folder was therefore treated as an administrator of every folder, and could list deleted dashboard items from folders they have no access to. On a shared observability stack - the common pattern where each tenant or team owns its own folder - this breaks the folder boundary that the separation relies on, leaking dashboard titles and contents from other teams' deleted work. Confidentiality and integrity of the authorization decision only; no code execution and no effect on running GPU workloads.

Who can reach it

Authenticated Grafana user who already has dashboard permission-management rights on at least one folder (the record scores privileges required as high), over HTTP to the Grafana API.

What to do

Upgrade Grafana to the version named in the vendor advisory and restart the service; the fix makes the check require permission on the specified folder, an ancestor, or a wildcard scope. This record carries no fixed version - take it from grafana.com/security/security-advisories/cve-2026-16491. Single-service restart, no fleet maintenance window. Reviewing who holds folder-level permission-management rights is a sensible follow-up, since that is the privilege that was being over-honoured.

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.