Nezha's authenticated DDNS webhook configuration allows blind SSRF from the dashboard host

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-47268: 0.22% estimated exploitation activity in the next 30 days; percentile 12.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary An authenticated Nezha dashboard user can create or update a DDNS profile with provider webhook and configure an arbitrary webhookurl, 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. Details The DDNS API is available to authenticated users, not only administrators: - cmd/dashboard/controller/controller.go:137 registers GET /api/v1/ddns. - cmd/dashboard/controller/controller.go:139 registers POST /api/v1/ddns. - cmd/dashboard/controller/controller.go:140 registers PATCH…

Published by the source

29 May 2026, 22:10 UTC

Last modified by the source

26 Jun 2026, 21:28 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6x26-5727-rrm9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47268

Advisory: Nezha's authenticated DDNS webhook configuration allows blind SSRF from the dashboard host
IDs: CVE-2026-47268, GHSA-6x26-5727-rrm9
Record: https://patchnext.com/advisories/cve-2026-47268 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/nezhahq/nezha 2.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nezhahq/nezha: affected >= 0.20.0, < 2.0.10; fixed in 2.0.10
- Go github.com/naiba/nezha: affected >= 0.20.0

## Suggested inspection (read-only)
- Go github.com/nezhahq/nezha: check the installed version with your package manager.
- Go github.com/naiba/nezha: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/nezhahq/nezha, github.com/naiba/nezha.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6x26-5727-rrm9 (GitHub-reviewed advisory GHSA-6x26-5727-rrm9 lists affected ranges: Go github.com/nezhahq/nezha >=0.20.0 =0.20.0)

Commands are suggestions: review each one before running it.