Menu

Star on GitHub · 3.2k

CVE-2026-72761

The webhook URL validator in `website/notifications/webhooks.py` uses `ip.is_global` to reject non-public addresses after DNS resolution.

Published Aug 10, 2026CWE-918EPSS 0.47%

Overview

CVE-2026-72761 is a known-severity vulnerability. It was published on August 10, 2026.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-72761?

CVE-2026-72761 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-72761?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-72761?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72761?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72761 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.