GPU VulnDB

Database/Control plane, storage & DevOps

Grafana Elasticsearch data source: extreme time range makes the server allocate memory until it dies

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

Impact

On an Elasticsearch data source with a time-based index pattern, Grafana generates one index name for every interval in the query time range, with no upper limit. A user who can query the data source (Viewer in a default configuration) can send one small query with an extreme time range and make the server allocate memory until it is killed. This happens before any request reaches Elasticsearch, so it works whether or not the cluster is reachable. The result is a low-privilege way to take down the monitoring and logging view of the fleet.

Who can reach it

An authenticated user with permission to query the Elasticsearch data source (Viewer by default), over the network.

What to do

Upgrade Grafana to a fixed release listed in the Grafana advisory and restart the Grafana server. The record names no fixed version. Data sources that use a static index name are not affected. Until you upgrade, restrict query permission on time-pattern Elasticsearch data sources.

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.