Tempo query limit results in unbounded memory allocation
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.6%
exploitation probability
0.6%top 51% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
https://access.redhat.com/errata/RHSA-2026:21769https://access.redhat.com/errata/RHSA-2026:22347https://access.redhat.com/errata/RHSA-2026:22423https://access.redhat.com/errata/RHSA-2026:23345https://access.redhat.com/errata/RHSA-2026:24503https://access.redhat.com/security/cve/CVE-2026-21728https://bugzilla.redhat.com/show_bug.cgi?id=2461395https://grafana.com/security/security-advisories/cve-2026-21728https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-21728.json