Advisory record · GHSA-4g6j-g789-rghm

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

CVSS 7.1 HighEPSS 0.0031 · 24th percentile

Published by the GitHub Advisory Database at 1 Jun 2026, 14:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nezhahq/nezhaGo>=0.20.0, <1.14.15-0.20260521020202-02129f16fb15 || >=2.0.0, <2.0.121.14.15-0.20260521020202-02129f16fb15, 2.0.12
Identifiers
GHSA-4g6j-g789-rghm · CVE-2026-48119 · GO-2026-5119
Weakness (CWE)
CWE-862
Published
1 Jun 2026
Updated
11 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nezha versions from 0.20.0 before 1.14.15-0.20260521020202-02129f16fb15, and from 2.0.0 before 2.0.12, are affected. An authenticated agent can submit forged service-monitor results for services it is not assigned to, including services owned by other users, which can corrupt their service history and current status and trigger notifications with attacker-controlled text. Upgrade to 1.14.15-0.20260521020202-02129f16fb15 or 2.0.12. The source gives no workaround.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 24th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:53 UTC First seen by agentprime
  2. 31 Oct 2026, 14:53 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.