CVE-2026-49396 json
Nezha Monitoring: Cross-site GET request can trigger stored cron commands on a victim's agents
published 2026-06-10 4 mo ago modified 2026-10-25 14 d ago also GHSA-8qhj-4f8c-j8qg , GO-2026-5261 , EUVD-2026-36596
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.0.0 to before version 2.0.14, cross-site GET request can trigger stored cron commands on a victim's agents. This issue has been patched in version 2.0.14.
Patch / fix
- go github.com/nezhahq/nezha 2.0.14
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/nezhahq/nezha/security/advisories/GHSA-8qhj-4f8c-j8qg 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:N/UI:R/S:U/C:N/I:H/A:L |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/nezhahq/nezha | >=1.0.0, <2.0.14 >=1.0.0 |
2.0.14 |
Affected products
- nezhahq nezha
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/nezhahq/nezha/security/advisories/GHSA-8qhj-4f8c-j8qg
exploit, web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-49396
advisory
-
github.com
/nezhahq/nezha
package
Sources
- CVE List CVE-2026-49396
- GitHub Advisory GHSA-8qhj-4f8c-j8qg
- NVD CVE-2026-49396
- OSV GO-2026-5261
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.