When an Elasticsearch data source is configured with a time-based index pattern, Grafana generated one index name for
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 12.4.15 when convenient.
Data as of 12 Nov 2026, 19:48 UTC
Thin evidence
One scorer or none| CNA (GRAFANA) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 12.4.15, 12.9.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade Grafana OSS and Grafana Enterprise to 12.4.15; Elasticsearch Datasource to 12.9.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GrafanaGrafana OSS | Affected
| Fixed in
|
| GrafanaElasticsearch Datasource | Affected
| Fixed in
|
| GrafanaGrafana Enterprise | Affected
| Fixed in
|
AI-suggested
Users should avoid configuring Elasticsearch data sources with time-based index patterns that allow unbounded index name generation or restrict query time ranges. Monitoring and limiting query time ranges for users with query permissions can mitigate the risk.
Description
Grafana versions configured with an Elasticsearch data source using a time-based index pattern can generate excessive index names for queries with large time ranges. This behavior can cause the server to allocate excessive memory, potentially leading to termination of the Grafana server process. The issue affects users with query permissions, including those with only Viewer role in default configurations. Data sources using static index names are not affected.