Information Disclosure in github.com/nezhahq/nezha (CVE-2026-47124)
Summary
Vulnerability in github.com/nezhahq/nezha (CVE-2026-47124). Confidential information can be exposed externally. Exploitable via GET /api/v1/server. Mitigation: upgrade to 1.14.15-0.20260517034128-05e5da253519 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.9, any authenticated non-admin member can connect to the server-status WebSocket and receive telemetry for all servers, including servers owned by other users. The normal server list API filters objects by HasPermission, but the WebSocket stream treats the presence of any authenticated user as authorization for the full unfiltered server list. This issue has been patched in version 2.0.9.
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-47124 has been found in github.com/nezhahq/nezha.
Attackers can target a specific entry point like GET /api/v1/server over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade github.com/nezhahq/nezha to 1.14.15-0.20260517034128-05e5da253519 or later.
If unsure, ask your IT team or search "github.com/nezhahq/nezha CVE-2026-47124" on the vendor's site.
CVE-2026-47124 (github.com/nezhahq/nezha) — CWE-200 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/server / GET /api/v1/ws/server / HasPermission / serverStream
Patched: 1.14.15-0.20260517034128-05e5da253519 — 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.
Information disclosure (CWE-200) exists in github.com/nezhahq/nezha. Attackers reach the vulnerable code path via GET /api/v1/server.
Check the vendor advisory for the affected versions of github.com/nezhahq/nezha. Attack surface: GET /api/v1/server / GET /api/v1/ws/server / HasPermission / serverStream.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 1.14.15-0.20260517034128-05e5da253519.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/server 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
-
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/server' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/serverへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/nezhahq/nezha to 1.14.15-0.20260517034128-05e5da253519ステージング環境で 1.14.15-0.20260517034128-05e5da253519 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/server on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com