CVE-2026-46717 Nezha Monitoring: RoleMember-reachable SSRF with full response-body reflection via POST /api/v1/notification
A RoleMember user can trigger Server-Side Request Forgery via notification endpoints, reading internal network responses due to missing authorization checks.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-46717?
CVE-2026-46717 is a high-severity server-side request forgery vulnerability in nezhahq nezha, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.4.0 to before version 2.0.8, nezha's dashboard supports two user roles: RoleAdmin (Role==0) and RoleMember (Role==1). The notification routes POST /api/v1/notification and PATCH /api/v1/notification/:id are wired through commonHandler rather than adminHandler — so a RoleMember user can call them. These handlers synchronously Send() an HTTP request to a user-controlled URL and reflect the entire response body (no size limit) back to the caller on any non-2xx response. This issue has been patched in version 2.0.8.
Which versions are affected by CVE-2026-46717?
3 open source packages ship an affected version, including github.com/nezhahq/nezha.
| Package | Affected | Fixed in |
|---|---|---|
github.com/nezhahq/nezha Go | From 1.4.0 | 1.14.15-0.20260517022419-d06d539d34c1 |
github.com/nezhahq/nezha Go | From 1.4.0 | 1.14.15-0.20260517022419-d06d539d34c1 |
github.com/nezhahq/nezha Go | From 1.4.0 | 1.14.15-0.20260517022419-d06d539d34c1 |
How do I fix CVE-2026-46717?
Upgrade github.com/nezhahq/nezha to 1.14.15-0.20260517022419-d06d539d34c1 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-46717 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46717 exists.
Sources
Also known as GHSA-w4g9-mxgg-j532, GO-2026-5687.