Advisory

GHSA-p4r4-xvrq-gvmc

Also known as: CVE-2026-21728, GO-2026-5528

Summary

Grafana Tempo has an Uncontrolled Resource Consumption issue

Details

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).

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-04-24 09:30 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/grafana/tempo

Go · All systems

Affected

  • introduced 1.3.0, fixed 2.8.4 (semver)

Fixed versions

2.8.4

Fix

github.com/grafana/tempo

Go · All systems

Affected

  • introduced 2.9.0, fixed 2.9.2 (semver)

Fixed versions

2.9.2

Fix

github.com/grafana/tempo

Go · All systems

Affected

  • introduced 2.10.0, fixed 2.10.2 (semver)

Fixed versions

2.10.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences