Skip to main content
VulnerabilityPublished Updated

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

Affects Grafana TempoSource CVE Database V5

0
Compare

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

Data as of 1 Nov 2026, 22:58 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.8.8, 2.10.2
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 19 Jun 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 1 Nov 2026.

What to do

Upgrade Tempo to 2.10.2; Enterprise Traces (GET) to 2.8.8.

Affected software

ProductAffectedFixed in
GrafanaEnterprise Traces (GET)Affected
  • >=2.6.1 <2.8.8
Fixed in
  • 2.8.8
GrafanaTempoAffected
  • >=2.6.0 <2.10.2
Fixed in
  • 2.10.2

AI-suggested

If you cannot patch yet, restrict access to authenticated users and monitor for abnormal query patterns that might trigger excessive memory use.

Description

A TraceQL query in Grafana Tempo with a large exemplars hint value can cause the Tempo instance to allocate an excessive amount of memory, resulting in an out-of-memory crash. This could allow an authenticated user to trigger a denial of service against the Tempo service.

References

Community reviews

Loading reviews…