CVE-2026-54452 safeurl: Missing IPv6 CIDR Ranges in Blocklist
Attackers can bypass SSRF protections in safeurl by targeting omitted IPv6 ranges when IPv6 support is explicitly enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54452?
CVE-2026-54452 is a medium-severity server-side request forgery vulnerability in doyensec safeurl, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
safeurl is a server-side request forgery protection library. Prior to 0.2.4, the privateNetworks list in ip.go omits the IPv6 ranges 64:ff9b:1::/48, 5f00::/16, 3fff::/20, and 100:0:0:1::/64. When an application enables IPv6 with EnableIPv6(true), an attacker-controlled destination in one of these ranges is not recognized as non-public and can pass the SSRF destination check, potentially allowing access to resources hosted within the omitted ranges. IPv6 is disabled by default, and configurations that retain EnableIPv6(false) are not exposed to this bypass. This issue is fixed in version 0.2.4.
Weakness: CWE-918
Which versions are affected by CVE-2026-54452?
3 open source packages ship an affected version, including github.com/doyensec/safeurl.
| Package | Affected | Fixed in |
|---|---|---|
github.com/doyensec/safeurl Go | All versions | 0.2.4 |
github.com/doyensec/safeurl Go | All versions | 0.2.4 |
github.com/doyensec/safeurl Go | All versions | 0.2.4 |
How do I fix CVE-2026-54452?
Upgrade github.com/doyensec/safeurl to 0.2.4 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-54452 being exploited?
There is no known exploitation of CVE-2026-54452 in the wild and no public exploit code.
Sources
Also known as GHSA-xgch-x3mx-cm3c, GO-2026-5997.