Grafana OSS and Grafana Enterprise did not safely resolve symbolic links when extracting plugin archives. A crafted plugin archive can chain relative symbolic link entries to escape the plugin installation directory, writing arbitrary files and an executable backend binary outside that directory. The dropped executable runs with the privileges of the Grafana server process, resulting in remote code execution.
Plugin archives are extracted before their signature is verified, so a valid plugin signature does not prevent the write. An operator can therefore be affected by installing a plugin that appears legitimate, as well as by installing a plugin from an arbitrary archive using grafana-cli, the GF_INSTALL_PLUGINS environment variable, or preinstall configuration.
Grafana Enterprise is affected because it includes the same plugin extraction code as Grafana OSS.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade grafanaUpgrade grafana-selinux | Oct 15, 2026 | Oct 15, 2026 |
| Oracle_linux | — | Upgrade grafanaUpgrade grafana-selinux | Oct 22, 2026 | Sep 17, 2026 |
| Redhat_linux | — | Upgrade grafana-selinuxNo solution existsUpgrade grafanaUpgrade grafana-debugsourceUpgrade grafana-debuginfo | Oct 5, 2026 | Sep 30, 2026 |
| Rocky_linux | — | Upgrade grafana-debugsourceUpgrade grafana-debuginfoUpgrade grafana-selinuxUpgrade grafana | Oct 19, 2026 | Oct 16, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub