Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-21728 high CVSS 7.5

Vulnerability in github.com/grafana/tempo (CVE-2026-21728)

Summary

vulnerability in github.com/grafana/tempo (CVE-2026-21728). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.10.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-21728** has been found in github.com/grafana/tempo. Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10. What to do: upgrade github.com/grafana/tempo to **2.10.2** or later. If unsure, ask your IT team or search "github.com/grafana/tempo CVE-2026-21728" on the vendor's site.
CVE-2026-21728 (github.com/grafana/tempo) — CWE-400 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Patched: `2.10.2` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-400) exists in github.com/grafana/tempo.
📍 Affected scope
github.com/grafana/tempo — .
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.10.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/grafana/tempo' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/grafana/tempo' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/grafana/tempo` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade github.com/grafana/tempo to 2.10.2

    ステージング環境で 2.10.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Go github.com/grafana/tempo
[{"type":"SEMVER","events":[{"introduced":"2.10.0"},{"fixed":"2.10.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →