CVE-2026-47268 Nezha Monitoring: Authenticated DDNS webhook configuration allows blind SSRF from the dashboard host
Authenticated users can trigger blind SSRF via DDNS webhooks, allowing internal network access from the dashboard host.
- 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-47268?
CVE-2026-47268 is a medium-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 0.20.0 to before version 2.0.10, an authenticated Nezha dashboard user can create or update a DDNS profile with provider webhook and configure an arbitrary webhook_url, HTTP method, request body, and headers. When DDNS is triggered for a server that uses that profile, the dashboard process sends the configured request with utils.HttpClient without the SSRF protections used by notification webhooks. This allows a low-privileged authenticated user who controls an owned server/DDNS profile to make the dashboard host issue HTTP requests to loopback or internal network services. The response body is not returned to the attacker in the confirmed path, so this is a blind SSRF / internal state-changing request primitive. This issue has been patched in version 2.0.10.
Weakness: CWE-918
Which versions are affected by CVE-2026-47268?
5 open source packages ship an affected version, including github.com/nezhahq/nezha and github.com/naiba/nezha.
| Package | Affected | Fixed in |
|---|---|---|
github.com/nezhahq/nezha Go | From 0.20.0 | 2.0.10 |
github.com/nezhahq/nezha Go | From 0.20.0 | 2.0.10 |
github.com/naiba/nezha Go | From 0.20.0 | None |
github.com/naiba/nezha Go | From 0.20.0 | None |
github.com/naiba/nezha Go | From 0.20.0 | None |
How do I fix CVE-2026-47268?
Upgrade github.com/nezhahq/nezha to 2.0.10 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-47268 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47268 exists.
Sources
Also known as GHSA-6x26-5727-rrm9, GO-2026-5194.