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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-p4r4-xvrq-gvmc
- OSV: GHSA-p4r4-xvrq-gvmc
- nvd.nist.gov/vuln/detail/CVE-2026-21728
- github.com/grafana/tempo/pull/6525
- github.com/grafana/tempo/commit/650eb1985a0776789c8564122990f588a742356f
- github.com/grafana/tempo
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-10.md?plain=1#L328
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-8.md?plain=1#L251
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-9.md?plain=1#L224
- grafana.com/security/security-advisories/cve-2026-21728