← Back
CVE-2026-53519
critical
CVSS 9.1
Path Traversal in github.com/nezhahq/nezha (CVE-2026-53519)
Summary
path traversal in github.com/nezhahq/nezha (CVE-2026-53519). Confidential information can be exposed externally. Exploitable via `GET /dashboard../data/config.yaml`. Mitigation: upgrade to `2.0.13` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53519** has been found in github.com/nezhahq/nezha.
Attackers can target a specific entry point like `GET /dashboard../data/config.yaml` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade github.com/nezhahq/nezha to **2.0.13** or later.
If unsure, ask your IT team or search "github.com/nezhahq/nezha CVE-2026-53519" on the vendor's site.
CVE-2026-53519 (github.com/nezhahq/nezha) — CWE-22 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /dashboard../data/config.yaml / GET /dashboard../data/sqlite.db / `fallbackToFrontend` / `NoRoute`
Patched: `2.0.13` — 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/nezhahq/nezha. Attackers reach the vulnerable code path via `GET /dashboard../data/config.yaml` without authentication.
📍 Affected scope
github.com/nezhahq/nezha — . Attack surface: GET /dashboard../data/config.yaml / GET /dashboard../data/sqlite.db / `fallbackToFrontend` / `NoRoute`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.0.13**.
🛡️ 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 `GET /dashboard../data/config.yaml` requests with malformed payloads or SQL meta-characters. Run `grep -r 'github.com/nezhahq/nezha' .` 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
-
1Identify exposure identify
grep -r 'github.com/nezhahq/nezha' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/nezhahq/nezha` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /dashboard../data/config.yaml' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /dashboard../data/config.yaml` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade github.com/nezhahq/nezha to 2.0.13ステージング環境で 2.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /dashboard../data/config.yaml on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/nezhahq/nezha
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.13"}]}]