NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Grafana Tempo has an Uncontrolled Resource Consumption issueGHSA-p4r4-xvrq-gvmc

HIGHFix: grafana/tempo#6525

GHSA-p4r4-xvrq-gvmc is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in github.com/grafana/tempo. A fix is available for github.com/grafana/tempo — see the affected versions and patch details below.

Also known asCVE-2026-21728GO-2026-5528
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p4r4-xvrq-gvmc.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk
0.14%0.47%0.80%1.14%0.6%0.6%0.6%Oct 26Nov 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐹github.com/grafana/tempo🐹github.com/grafana/tempo🐹github.com/grafana/tempo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/tempo≥ 1.3.0&&< 2.8.42.8.4go get github.com/grafana/tempo@v2.8.4
🐹Gogithub.com/grafana/tempo≥ 2.9.0&&< 2.9.22.9.2go get github.com/grafana/tempo@v2.9.2
🐹Gogithub.com/grafana/tempo≥ 2.10.0&&< 2.10.22.10.2go get github.com/grafana/tempo@v2.10.2

Affected Products

1 product · 3 configurations
Application
tempografana
≥ 2.10.0 && < 2.10.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/tempo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/grafana/tempo to 2.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p4r4-xvrq-gvmc is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as having an Important security impact because remote unauthenticated actors can send queries configured with excessively large limit values, inducing unbounded memory consumption that results in a denial of service. In Red Hat OpenShift distributed tracing environments, components exposing…

ProductFixed inAdvisory
Multicluster Global Hub 1.3.4multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779212259RHSA-2026:22423
Multicluster Global Hub 1.4.9multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779579439RHSA-2026:22347
Multicluster Global Hub 1.5.8multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1778867753RHSA-2026:21769
Multicluster Global Hub 1.6.6multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1780167118RHSA-2026:23345
Multicluster Global Hub 1.7.3multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779925273RHSA-2026:24503

Frequently Asked Questions

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).
O3 Security · Impact-Aware SCA

Is GHSA-p4r4-xvrq-gvmc in your dependencies?

Find it across Go, including transitive dependencies.

Grafana Tempo has an Uncontrolled Resource…