Categories
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.

Original description

The description as published by the source.

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. Prior to version 2.0.13, fallbackToFrontend in the dashboard's NoRoute handler treats any URL whose raw string starts with /dashboard as an admin-frontend asset request. The check uses strings.HasPrefix, not a path-segment match, so the input /dashboard../data/config.yaml is accepted; strings.TrimPrefix leaves ../data/config.yaml; and path.Join("admin-dist", "../data/config.yaml") normalizes to data/config.yaml — which os.Stat finds and http.ServeFile returns. No authentication required. This issue has been patched in version 2.0.13.

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-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

Check the vendor advisory for the affected versions of 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

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt 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 があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade github.com/nezhahq/nezha to 2.0.13

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

  4. 4
    Post-deployment verification verify
    Replay attack against GET /dashboard../data/config.yaml on staging to confirm patch closes the vector

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

Affected packages

go github.com/nezhahq/nezha
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.0.13"}]}]

References

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