Categories
CVE-2026-47268 medium CVSS 6.4

SSRF (Server-Side Request Forgery) in github.com/nezhahq/nezha (CVE-2026-47268)

Summary

SSRF in github.com/nezhahq/nezha (CVE-2026-47268). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/ddns. Mitigation: upgrade to 2.0.10 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. From version 0.20.0 to before version 2.0.10, an authenticated Nezha dashboard user can create or update a DDNS profile with provider webhook and configure an arbitrary webhook_url, HTTP method, request body, and headers. When DDNS is triggered for a server that uses that profile, the dashboard process sends the configured request with utils.HttpClient without the SSRF protections used by notification webhooks. This allows a low-privileged authenticated user who controls an owned server/DDNS profile to make the dashboard host issue HTTP requests to loopback or internal network services. The response body is not returned to the attacker in the confirmed path, so this is a blind SSRF / internal state-changing request primitive. This issue has been patched in version 2.0.10.

Source: GitHub Security Advisories (Global) 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-47268 has been found in github.com/nezhahq/nezha.
Attackers can target a specific entry point like GET /api/v1/ddns over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: upgrade github.com/nezhahq/nezha to 2.0.10 or later.
If unsure, ask your IT team or search "github.com/nezhahq/nezha CVE-2026-47268" on the vendor's site.

CVE-2026-47268 (github.com/nezhahq/nezha) — CWE-918 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/ddns / POST /api/v1/ddns / PATCH /api/v1/ddns/ / POST /internal
Patched: 2.0.10 — 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

SSRF (CWE-918) exists in github.com/nezhahq/nezha. Attackers reach the vulnerable code path via GET /api/v1/ddns.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/nezhahq/nezha. Attack surface: GET /api/v1/ddns / POST /api/v1/ddns / PATCH /api/v1/ddns/ / POST /internal.

🔥 Severity

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

🔧 How to fix

Update to 2.0.10.

🛡️ 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 /api/v1/ddns 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 /api/v1/ddns' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/v1/ddns への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

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

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

  4. 4
    Post-deployment verification verify
    Replay attack against GET /api/v1/ddns on staging to confirm patch closes the vector

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

Affected packages

go github.com/nezhahq/nezha
[{"type":"SEMVER","events":[{"introduced":"0.20.0"},{"fixed":"2.0.10"}]}]
go github.com/naiba/nezha
[{"type":"SEMVER","events":[{"introduced":"0.20.0"}]}]

References

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