Categories
CVE-2026-46717 high CVSS 7.7

Authorization Flaw in github.com/nezhahq/nezha (CVE-2026-46717)

Summary

Vulnerability in github.com/nezhahq/nezha (CVE-2026-46717). Confidential information can be exposed externally. Exploitable via POST /api/v1/notification. Mitigation: upgrade to 1.14.15-0.20260517022419-d06d539d34c1 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 1.4.0 to before version 2.0.8, nezha's dashboard supports two user roles: RoleAdmin (Role==0) and RoleMember (Role==1). The notification routes POST /api/v1/notification and PATCH /api/v1/notification/:id are wired through commonHandler rather than adminHandler — so a RoleMember user can call them. These handlers synchronously Send() an HTTP request to a user-controlled URL and reflect the entire response body (no size limit) back to the caller on any non-2xx response. This issue has been patched in version 2.0.8.

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-46717 has been found in github.com/nezhahq/nezha.
Attackers can target a specific entry point like POST /api/v1/notification over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/nezhahq/nezha to 1.14.15-0.20260517022419-d06d539d34c1 or later.
If unsure, ask your IT team or search "github.com/nezhahq/nezha CVE-2026-46717" on the vendor's site.

CVE-2026-46717 (github.com/nezhahq/nezha) — CWE-863 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/notification / PATCH /api/v1/notification/ / PATCH /notification/ / RoleAdmin
Patched: 1.14.15-0.20260517022419-d06d539d34c1 — 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

Incorrect authorization (CWE-863) exists in github.com/nezhahq/nezha. Attackers reach the vulnerable code path via POST /api/v1/notification.

📍 Affected scope

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

🔥 Severity

Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.14.15-0.20260517022419-d06d539d34c1.

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

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

  3. 3
    Apply patch patch
    Upgrade github.com/nezhahq/nezha to 1.14.15-0.20260517022419-d06d539d34c1

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

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

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

Affected packages

go github.com/nezhahq/nezha
[{"type":"SEMVER","events":[{"introduced":"1.4.0"},{"fixed":"1.14.15-0.20260517022419-d06d539d34c1"}]}]

References

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