# 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.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-6x26-5727-rrm9, GO-2026-5194

## 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 (Server-Side Request Forgery)

## 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 | Ecosystem | 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.

## Is CVE-2026-47268 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47268 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47268 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47268 exists.

Affected packages and fixed versions:
- github.com/nezhahq/nezha (Go): affected from 0.20.0; fixed in 2.0.10
- github.com/nezhahq/nezha (Go): affected from 0.20.0; fixed in 2.0.10
- github.com/naiba/nezha (Go): affected from 0.20.0; no fix listed
- github.com/naiba/nezha (Go): affected from 0.20.0; no fix listed
- github.com/naiba/nezha (Go): affected from 0.20.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47268/ (Markdown: https://insights.sbomify.com/CVE-2026-47268/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47268
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47268
- OSV: https://osv.dev/vulnerability/CVE-2026-47268

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47268/
Summaries are generated and may contain mistakes; the official description above is the record.