Advisory record · GHSA-p4r4-xvrq-gvmc

Grafana Tempo has an Uncontrolled Resource Consumption issue

CVSS 7.5 HighEPSS 0.0064 · 51st percentile

Published by the GitHub Advisory Database at 24 Apr 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/grafana/tempoGo>=1.3.0, <2.8.4 || >=2.9.0, <2.9.2 || >=2.10.0, <2.10.22.8.4, 2.9.2, 2.10.2
Identifiers
GHSA-p4r4-xvrq-gvmc · CVE-2026-21728 · GO-2026-5528
Weakness (CWE)
CWE-400 · CWE-770
Published
24 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Grafana Tempo versions from 1.3.0 before 2.8.4, from 2.9.0 before 2.9.2, and from 2.10.0 before 2.10.2 are affected. An attacker who can send queries with large limit values can trigger large memory allocations, which can hurt service availability depending on how Tempo is deployed. Upgrade to 2.8.4, 2.9.2, or 2.10.2 depending on your release line. As a workaround, set max_result_limit in the search configuration.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GRAFANA)
  • CISA KEV Not listed.
  • EPSS 0.0064, the 51st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.