CVE-2026-101087

Source
https://cve.org/CVERecord?id=CVE-2026-101087
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-101087.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-101087
Aliases
  • GHSA-jr2j-7hvh-h4q9
Published
2026-09-27T20:49:58Z
Modified
2026-09-29T03:45:57Z
Severity
  • 5.3 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L CVSS Calculator
Summary
Nezha 2.0.10 through 2.3.2 SSRF Denylist Bypass IPv6
Details

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.

Database specific
{
    "cna_assigner":  "VulnCheck",
    "cwe_ids":  [
        "CWE-918"
    ],
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/101xxx/CVE-2026-101087.json"
}
References

Affected packages

Git / github.com/nezhahq/nezha

Affected ranges

Type
GIT
Repo
https://github.com/nezhahq/nezha
Events
Database specific
Show details
{
    "extracted_events":  [
        {
            "introduced":  "2.0.10"
        },
        {
            "fixed":  "2.3.3"
        }
    ],
    "source":  "AFFECTED_FIELD"
}

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-101087.json"