Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-101087— Nezha 2.0.10 through 2.3.2 SSRF Denylist Bypass IPv6

Quick assessment

Affected
nezhahq nezha
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

哪吒（Nezha）版本 2.0.10 至 2.3.2 使用受限的 HTTP 客户端来验证用户可配置的 Webhook 通知和动态 DNS（DDNS）URL。然而，其拒绝列表（denylist）未涵盖 IPv6 过渡地址范围，具体包括 6to4 前缀 2002::/16 以及用于 IPv4/IPv6 转换的本地使用前缀 64:ff9b:1::/48。由于这些地址能够通过 Go 语言 netip.Addr 类型的 IsGlobalUnicast 检查，URL 验证器会错误地接受它们。 经过身份验证的用户若能配置 Web

CVSS 4.3 · Medium

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-101087

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Nezha 2.0.10 through 2.3.2 SSRF Denylist Bypass IPv6
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
服务端请求伪造(SSRF)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
nezhahq nezha 2.0.10 ~ 2.3.3 -

II. Public POCs for CVE-2026-101087

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-101087

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-101087 (1)

Other References for CVE-2026-101087 (2)

Same Patch Batch · nezhahq · 2026-09-27 · 6 CVEs total

CVE-2026-101090 9.8 CRITICAL Nezha through 2.2.3 Host Header Injection via OAuth2 redirect_uri
CVE-2026-101085 6.5 MEDIUM Nezha before 2.3.8 Denial of Service via Alert Rule
CVE-2026-101086 6.5 MEDIUM Nezha Dashboard before 2.3.5 Task Type Validation Bypass
CVE-2026-101088 5.3 MEDIUM Nezha before 2.3.1 Denial of Service via Concurrent Server Delete
CVE-2026-101089 3.1 LOW Nezha before 2.2.7 Information Disclosure via /api/v1/profile

IV. Related Vulnerabilities

Same product: nezha
Same vendor: nezhahq
Same weakness: CWE-918

V. Comments for CVE-2026-101087

No comments yet

Leave a comment