Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48119 high CVSS 7.1

Vulnerability in github.com/nezhahq/nezha (CVE-2026-48119)

Summary

Vulnerability in github.com/nezhahq/nezha (CVE-2026-48119). Data can be tampered with by attackers. Exploitable via TaskResult. Mitigation: upgrade to 2.0.12 or later.

Original description

The description as published by the source.

Summary

Nezha accepts service-monitor TaskResult messages from an authenticated agent based only on whether the reported service ID exists. The dashboard authenticates the agent and derives the reporter server ID from the gRPC stream, but the service-monitor result worker does not verify that the reporter server was selected for that service, belongs to the service owner, or was actually assigned that monitoring task.

A low-privilege user with a valid agent secret and one registered agent can therefore submit forged monitoring results for another user's service ID. This allows cross-tenant corruption of service-monitor history/current state, and can influence victim-owned service notifications with attacker-controlled result text.

Details

The agent task stream accepts inbound TaskResult messages after authenticating agent metadata:

  • service/rpc/auth.go:23-60 validates client_secret and client_uuid.
  • service/rpc/auth.go:63-75 registers an unknown valid UUID as a server for the authenticated secret owner.
  • service/rpc/nezha.go:40-48 authenticates the RequestTask stream and binds it to clientID.
  • service/rpc/nezha.go:50-56 receives agent-controlled TaskResult messages.
  • proto/nezha.proto:60-65 defines attacker-controlled TaskResult.id, type, delay, data, and successful.

For service-monitor task types, the result is dispatched directly to the service sentinel using the authenticated server ID as reporter:

  • `service/rpc/nezh…

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-48119 has been found in github.com/nezhahq/nezha.
Attackers can target a specific entry point like TaskResult over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade github.com/nezhahq/nezha to 2.0.12 or later.
If unsure, ask your IT team or search "github.com/nezhahq/nezha CVE-2026-48119" on the vendor's site.

CVE-2026-48119 (github.com/nezhahq/nezha) — CWE-862 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: TaskResult / client_secret / client_uuid / RequestTask
Patched: 2.0.12 — 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

A vulnerability (CWE-862) exists in github.com/nezhahq/nezha. Attackers reach the vulnerable code path via TaskResult.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/nezhahq/nezha. Attack surface: TaskResult / client_secret / client_uuid / RequestTask.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2.0.12.

🛡️ 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 request patterns matching this CVE's known IOCs. 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
    Apply patch patch 
    Upgrade github.com/nezhahq/nezha to 2.0.12

    ステージング環境で 2.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go github.com/nezhahq/nezha
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.0.12"}]}]
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