Skip to main content
VulnerabilityPublished Updated

CVE-2026-21728: Grafana Tempo · Uncontrolled Resource Consumption

Affects Grafana TempoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GrafanaTempoAffected
  • >=1.3.0 <=2.8.3
  • >=2.9.0 <=2.9.1
  • >=2.10.0 <=2.10.1
Fixed in–
GrafanaEnterprise Traces (GET)Affected
  • >=1.0.0 <=2.8.7
Fixed in–

AI-suggested

Mitigation can be implemented by setting the max_result_limit parameter in the Tempo search configuration to limit the size of queries, for example to 262144 (2^18). Alternatively, configuring the service to automatically restart can help recover from resource exhaustion. Users should monitor vendor advisories for any forthcoming official fixes or updates. Red Hat has issued security advisories referencing this CVE and recommends applying updates when available.

Description

Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.

References

Community reviews

Loading reviews…