Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

Nezha's authenticated agents can forge service-monitor results for other users' services

CVE-2026-48119GHSA-4g6j-g789-rghm

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/nezhahq/nezha

    Affected
    >= 0.20.0, < 1.14.15-0.20260521020202-02129f16fb15>= 2.0.0, < 2.0.12
    Fixed in
    1.14.15-0.20260521020202-02129f16fb15, 2.0.12

  • Go github.com/naiba/nezha

    Affected
    >= 0.20.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
EPSS
  • CVE-2026-48119: 0.31% estimated exploitation activity in the next 30 days; percentile 24.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 clientsecret and clientuuid. - service/rpc/auth.go:63-75 registers an unknown valid UUID as a server for the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-4g6j-g789-rghm

  2. Revision 1 · created ·

    Published from osv record GO-2026-5119

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48119

Advisory: Nezha's authenticated agents can forge service-monitor results for other users' services
IDs: CVE-2026-48119, GHSA-4g6j-g789-rghm
Record: https://patchnext.com/advisories/cve-2026-48119 (revision 2, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/nezhahq/nezha 2.0.12, 1.14.15-0.20260521020202-02129f16fb15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nezhahq/nezha: affected >= 0.20.0, < 1.14.15-0.20260521020202-02129f16fb15; >= 2.0.0, < 2.0.12; fixed in 1.14.15-0.20260521020202-02129f16fb15, 2.0.12
- Go github.com/naiba/nezha: affected >= 0.20.0

## Suggested inspection (read-only)
- Go github.com/nezhahq/nezha: check the installed version with your package manager.
- Go github.com/naiba/nezha: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/nezhahq/nezha, github.com/naiba/nezha.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-5119 (OSV record GO-2026-5119 lists affected ranges: Go github.com/naiba/nezha >=0.20.0; Go github.com/nezhahq/nezha >=1.0.0 <1.14.15-0.20260521020202-02129f16fb15 (fixed))
- Verified: https://github.com/advisories/GHSA-4g6j-g789-rghm (GitHub-reviewed advisory GHSA-4g6j-g789-rghm lists affected ranges: Go github.com/nezhahq/nezha >=0.20.0 =2.0.0 <2.0.12)

Commands are suggestions: review each one before running it.

Loading voting…