GPU VulnDB

Database/Control plane, storage & DevOps

Grafana: injected timeGroup macro in a SQL query exhausts memory and kills the server process

CVE-2026-19475Control plane, storage & DevOpscurated

Impact

Any user allowed to query a Microsoft SQL Server, PostgreSQL or MySQL data source can smuggle the timeGroup macro in through a WHERE clause, which Grafana's regex-based macro parsing fails to reject - bypassing the fix shipped for CVE-2026-33375. Evaluating the injected macro consumes memory without bound until the Grafana process is terminated, taking every dashboard and Grafana-managed alert rule down for all users at once. On a GPU fleet that means losing DCGM, thermal and job telemetry plus the alerting path exactly when operators need it, though the GPUs and workloads themselves keep running. Availability only - the advisory claims no data access or integrity impact.

Who can reach it

Authenticated Grafana user holding query permission on any SQL data source; a Viewer with Explore access is often enough. No administrator rights required.

What to do

Upgrade to the fixed Grafana release for CVE-2026-19475 - the earlier CVE-2026-33375 fix does not cover this path, so an instance patched only for that one is still exposed. Cost is a Grafana service restart, no fleet maintenance. Until then, narrowing who holds query permission on the SQL data sources reduces who can trigger it, and running Grafana under a memory limit with automatic restart turns a sustained outage into a brief one.

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.