GPU VulnDB

Database/Control plane, storage & DevOps

Grafana: symlink escape in plugin archive extraction gives remote code execution as the Grafana process

CVSS 8.8CVE-2026-15815Control plane, storage & DevOpscurated

Impact

A crafted plugin archive chains relative symlink entries to write files outside the plugin directory, including an executable backend binary that Grafana then runs with the privileges of the server process. Archives are extracted before their signature is checked, so a valid signature offers no protection and an operator installing a plausible-looking plugin is enough. Grafana is the fleet observability front end in most GPU datacenters and usually holds datasource credentials for Prometheus, DCGM exporters, Loki and cloud backends - code execution there hands an attacker the monitoring plane and its stored secrets. Grafana Enterprise ships the same extraction code and is equally affected.

Who can reach it

Anyone who can get an operator to install a plugin - from the catalog, from an arbitrary archive via grafana-cli, via GF_INSTALL_PLUGINS, or via preinstall configuration. No Grafana authentication is needed by the attacker; the trigger is the install action itself.

What to do

Upgrade Grafana OSS/Enterprise to the fixed release named in the vendor advisory and restart the Grafana service; no node drain is involved. Until then, do not install plugins from outside a trusted, vetted source, and treat GF_INSTALL_PLUGINS and preinstall lists in your deployment manifests as code paths that need review. Rotate datasource credentials if you suspect an untrusted plugin was ever installed.

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.