Skip to content
Fencer Vulns
high 7.1

CVE-2026-48119 json

Nezha Monitoring: Authenticated agents can forge service-monitor results for other users' services

published 2026-06-01 5 mo ago modified 2026-10-25 14 d ago also GHSA-4g6j-g789-rghm , GO-2026-5119 , EUVD-2026-36595

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 0.20.0 to before version 2.0.12, authenticated agents can forge service-monitor results for other users' services. This issue has been patched in version 2.0.12.

Patch / fix

  • go github.com/nezhahq/nezha 1.14.15-0.20260521020202-02129f16fb15, 2.0.12
  • govulncheck-vulndb SLES for SAP applications 16.0, SLES 16.0 0.0.20260827T195228-160000.1.1

suse advisories SUSE-SU-2026:23625-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260827T195228-160000.1.1

opensuse advisories openSUSE-SU-2026:21761-1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/nezhahq/nezha/security/advisories/GHSA-4g6j-g789-rghm referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
GitHub 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Affected packages

ecosystem package affected fixed in
go github.com/nezhahq/nezha
>=0.20.0, <1.14.15-0.20260521020202-02129f16fb15
>=2.0.0, <2.0.12
>=1.0.0, <1.14.15-0.20260521020202-02129f16fb15
1.14.15-0.20260521020202-02129f16fb15
2.0.12
go github.com/naiba/nezha
>=0.20.0
no fix listed

Affected products

  • nezhahq nezha

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.