Skip to main content
VulnerabilityPublished

CVE-2026-81843: Grafana OSS · Unthrottled Resource Allocation

Affects Grafana OSSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 12.4.15 when convenient.

Data as of 12 Nov 2026, 17:49 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GRAFANA)CVSS 3.16.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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GrafanaGrafana OSSAffected
  • >=11.6.0 <=11.6.16
  • >=12.0.0 <=12.2.10
  • >=12.3.0 <12.4.15
Fixed in
  • 12.4.15
GrafanaElasticsearch DatasourceAffected
  • >=12.4.2 <12.9.6
Fixed in
  • 12.9.6
GrafanaGrafana EnterpriseAffected
  • >=11.6.0 <=11.6.16
  • >=12.0.0 <=12.2.10
  • >=12.3.0 <12.4.15
Fixed in
  • 12.4.15

AI-suggested

Upgrade Grafana OSS to version 12.4.15 or later, or 12.9.6 or later, where this vulnerability is fixed. No other mitigation is indicated. Users should ensure that data sources with time-based index patterns are updated to fixed versions to prevent resource exhaustion.

Description

A resource allocation vulnerability exists in Grafana OSS when using an Elasticsearch data source with a time-based index pattern. A user with query permissions, including those with only Viewer role, can submit a query with an extremely large time range, causing Grafana to generate many index names and allocate excessive memory. This allocation happens before any request is sent to Elasticsearch, potentially leading to server termination due to resource exhaustion. Data sources with static index names are not affected. The issue affects multiple versions of Grafana OSS and has been fixed in versions 12.4.15 and 12.9.6.

References

Community reviews

Loading reviews…