The webhook URL validator in `website/notifications/webhooks.py` uses `ip.is_global` to reject non-public addresses…
Summary
SSRF reported (CVE-2026-72761). Risk of unauthorized operations or information disclosure. Exploitable via ip.is_global.
Original description
The description as published by the source.
The webhook URL validator in website/notifications/webhooks.py uses
ip.is_global to reject non-public addresses after DNS resolution. IPv6
transition addresses (NAT64 64:ff9b::/96, 6to4 2002::/16, Teredo
2001:0000::/32) are classified as globally routable by IANA, so is_global
returns True even when the embedded IPv4 targets a private, loopback, or
cloud metadata destination. An attacker can register a webhook pointing at a
hostname that resolves to a transition address to bypass the SSRF guard and
exfiltrate vulnerability data to an internal endpoint.
The vulnerability was introduced on a non-release version. The fix was already done on HEAD. It only affects
organisation running the HEAD.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-72761 has been found.
Attackers can target a specific entry point like ip.is_global over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-72761" on the vendor's site.
CVE-2026-72761 — CWE-918
Attack surface: ip.is_global / is_global / True
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) has been reported. Attackers reach the vulnerable code path via ip.is_global.
Check the vendor advisory for the affected versions. Attack surface: ip.is_global / is_global / True.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com