Advisory

GO-2026-5119

Also known as: CVE-2026-48119, GHSA-4g6j-g789-rghm

Summary

Nezha's authenticated agents can forge service-monitor results for other users' services in github.com/nezhahq/nezha

Details

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 submit forged monitoring results for another user's service ID. This allows cross-tenant corruption of service-monitor history and state, and can influence victim-owned service notifications.

Severity

Not rated by the source.

Dates

Published
2026-08-11 20:19 UTC
Modified
2026-08-11 20:45 UTC

Affected packages and fixes

github.com/naiba/nezha

Go · All systems

Affected

  • introduced 0.20.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/nezhahq/nezha

Go · All systems

Affected

  • introduced 1.0.0, fixed 1.14.15-0.20260521020202-02129f16fb15 (semver)

Fixed versions

1.14.15-0.20260521020202-02129f16fb15

Fix

  • Fixed version 1.14.15-0.20260521020202-02129f16fb15
    go get github.com/nezhahq/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Go Vulnerability Database · CC BY 4.0

Sources & licences