CVE-2026-101087

published 27 Sep 2026 · updated 30 Sep 2026

Nezha 2.0.10 through 2.3.2 SSRF Denylist Bypass IPv6

4.3MediumCVSS 4.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.3.3.

Nezha versions 2.0.10 through 2.3.2 use a restricted HTTP client to validate user-configurable notification and DDNS webhook URLs, but the denylist did not cover IPv6 transition ranges — specifically the 6to4 prefix 2002::/16 and the local-use IPv4/IPv6 translation prefix 64:ff9b:1::/48. Because such addresses satisfy Go's netip.Addr.IsGlobalUnicast check, the URL validator accepted them. An authenticated user able to configure a webhook may be able to cause the dashboard to issue requests to an otherwise restricted IPv6 endpoint, but only where the dashboard's network provides unusual or non-standards-compliant routing for these transition ranges; no direct path to an IPv4 metadata, loopback, or private-network HTTP request has been demonstrated. The issue is fixed in version 2.3.3 (commit d1fcde8e), which blocks both prefixes.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nezhahq>=2.0.10 <2.3.32.3.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-101087 severity on Zeptric[![CVE-2026-101087](https://zeptric.io/badge/cve/CVE-2026-101087.svg)](https://zeptric.io/cve/CVE-2026-101087)