CVE-2026-54452: doyensec safeurl · Server-Side Request Forgery (SSRF)
Affects doyensec safeurlSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.2.4 when convenient.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-09-16.
- Patch
- Available – fixed in 0.2.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade doyensec safeurl to 0.2.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| doyensecsafeurl | Affected
| Fixed in
|
AI-suggested
Upgrade safeurl to version 0.2.4 or later, where the omitted IPv6 ranges are properly included in the privateNetworks list, preventing SSRF bypass. If upgrading is not immediately possible, ensure that IPv6 support remains disabled (EnableIPv6(false)) to avoid exposure to this vulnerability.
Description
CVE-2026-54452 is a Server-Side Request Forgery (SSRF) vulnerability in the safeurl library prior to version 0.2.4. The vulnerability arises because certain IPv6 address ranges were omitted from the privateNetworks list, allowing attackers to bypass SSRF destination checks when IPv6 is enabled. This could potentially allow unauthorized access to internal resources within those omitted IPv6 ranges. IPv6 is disabled by default, so systems not enabling it are not affected. The issue is fixed in safeurl version 0.2.4.
References
- github.com/doyensec/safeurl/security/advisories/GHSA-xgch-x3mx-cm3c (opens in a new tab)
- github.com/doyensec/safeurl/pull/12 (opens in a new tab)
- github.com/doyensec/safeurl/commit/d8f1021ea535b276f92999f0ec865da40e467016 (opens in a new tab)
- github.com/doyensec/safeurl/releases/tag/v0.2.4 (opens in a new tab)