Vulnerability in github.com/nezhahq/nezha (CVE-2026-100394)
Summary
Vulnerability in github.com/nezhahq/nezha (CVE-2026-100394). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1/service. Mitigation: upgrade to 2.2.11 or later.
Original description
The description as published by the source.
Summary
A single low-privilege RoleMember can take the entire Nezha dashboard offline, and with it every tenant's web UI, REST API, and agent connections, by racing two ordinary operations on their own service. The crash is a nil pointer dereference in the service-monitor worker at service/singleton/servicesentinel.go:601. The worker checks a service exists under one lock and later writes to two pointer-valued status maps under a different lock; a concurrent delete removes the entries in the gap. Because the gRPC server has no recovery interceptor, the worker-goroutine panic kills the whole process. Availability only: nothing is read or modified.
Affected versions
Confirmed in v2.2.7 through v2.2.10. service/singleton/servicesentinel.go has the same vulnerable implementation in all four releases. The issue is fixed in v2.2.11 and later; users should upgrade to the latest release, v2.3.0.
The bug
The worker validates an incoming report and later writes it to two status maps, but the check and the write are guarded by two different locks taken at two different times. Between them, the same member can delete the service and pull the map entries out from under the worker.
The maps hold pointers, so a missing key returns nil and the first field write through it panics:
73: serviceStatusToday map[uint64]*_TodayStatsOfService
74: serviceCurrentStatusData map[uint64]*serviceTaskStatus
The worker checks presence via Get, which takes `s…
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-100394 has been found in github.com/nezhahq/nezha.
Attackers can target a specific entry point like POST /api/v1/service over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade github.com/nezhahq/nezha to 2.2.11 or later.
If unsure, ask your IT team or search "github.com/nezhahq/nezha CVE-2026-100394" on the vendor's site.
CVE-2026-100394 (github.com/nezhahq/nezha) — CWE-362 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/service / POST /api/v1/batch-delete/service / GET /api/v1/user / RoleMember
Patched: 2.2.11 — 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.
A vulnerability (CWE-362) exists in github.com/nezhahq/nezha. Attackers reach the vulnerable code path via POST /api/v1/service.
Check the vendor advisory for the affected versions of github.com/nezhahq/nezha. Attack surface: POST /api/v1/service / POST /api/v1/batch-delete/service / GET /api/v1/user / RoleMember.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.2.11.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/service 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 'POST /api/v1/service' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/serviceへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/nezhahq/nezha to 2.2.11ステージング環境で 2.2.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/service on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com