Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-10601 medium CVSS 5.4

Path Traversal in github.com/grafana/grafana (CVE-2026-10601)

Summary

Path traversal in github.com/grafana/grafana (CVE-2026-10601). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.9.2-0.20260616075434-82ef13993059 or later.

Original description

The description as published by the source.

The Tempo and Loki datasource plugins construct backend HTTP requests by interpolating user-supplied input into URL paths without sanitization, enabling path traversal. A Viewer-role user can: (1) capture admin-configured datasource credentials (secureJsonData custom headers) by traversing to an attacker-controlled endpoint, (2) invoke state-changing admin endpoints on Tempo (e.g. /flush, /shutdown), and (3) exfiltrate internal service data via Loki's CallResource which returns full HTTP response bodies.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-10601 has been found in github.com/grafana/grafana.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade github.com/grafana/grafana to 1.9.2-0.20260616075434-82ef13993059 or later.
If unsure, ask your IT team or search "github.com/grafana/grafana CVE-2026-10601" on the vendor's site.

CVE-2026-10601 (github.com/grafana/grafana) — CWE-22 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.9.2-0.20260616075434-82ef13993059 — 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

Path traversal (CWE-22) exists in github.com/grafana/grafana.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/grafana/grafana.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.9.2-0.20260616075434-82ef13993059.

🛡️ 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/grafana' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

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

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

  2. 2
    Apply patch patch 
    Upgrade github.com/grafana/grafana to 1.9.2-0.20260616075434-82ef13993059

    ステージング環境で 1.9.2-0.20260616075434-82ef13993059 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

go github.com/grafana/grafana
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.2-0.20260616075434-82ef13993059"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details