Tempo vulnerability

What happened

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 versions

Tempo: 1.3.0 through 2.8.3 (semver); 2.9.0 through 2.9.1 (semver); 2.10.0 through 2.10.1 (semver); 1.0.0 through 2.8.7 (semver) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.