GPU VulnDB

Database/Control plane, storage & DevOps

Grafana Image Renderer: unvalidated filePath on /render/csv writes a shared object that Chromium then loads

CVSS 9.9CVE-2025-11539Control plane, storage & DevOpscurated

Impact

The /render/csv endpoint does not validate filePath, so a caller can write a shared object to an arbitrary location which the renderer's Chromium process then loads - arbitrary file write escalating to code execution as the renderer service. Exploitation needs only that the default authToken is unchanged or known and that the attacker can reach the renderer endpoint, and the renderer is routinely deployed as a sidecar or internal service that nobody treats as attack surface. On a fleet this lands inside the observability plane, which by design can reach every monitored node and often holds datasource credentials for the whole cluster, so the scope change in the vector (S:C) is real rather than theoretical. Affects grafana-image-renderer 1.0.0 through 4.0.16.

Who can reach it

Anyone with network reach to the image renderer endpoint who knows the authToken - which on default installs is the published default value. Typically that is anyone on the internal monitoring network; no Grafana user account needed.

What to do

Upgrade grafana-image-renderer to 4.0.17 and restart the renderer - a container or service restart, no node drain. Also change authToken away from the default and keep the renderer bound to the Grafana backend only, not to a general internal network; both are config changes plus a restart.

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.