What is CVE-2026-54452?

CVE-2026-54452 is a medium-severity server-side request forgery (SSRF) vulnerability in github.com/doyensec/safeurl (go), affecting versions < 0.2.4. It is fixed in 0.2.4. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

Which versions of github.com/doyensec/safeurl are affected by CVE-2026-54452?

github.com/doyensec/safeurl (go) versions < 0.2.4 is affected.

Is there a fix for CVE-2026-54452?

Yes. CVE-2026-54452 is fixed in 0.2.4. Upgrade to this version or later.

Is CVE-2026-54452 exploitable, and should I be worried?

Whether CVE-2026-54452 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-54452 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-54452 in github.com/doyensec/safeurl

Q: Which versions of github.com/doyensec/safeurl are affected by CVE-2026-54452?

github.com/doyensec/safeurl (go) versions < 0.2.4 is affected.

Q: Is there a fix for CVE-2026-54452?

Yes. CVE-2026-54452 is fixed in 0.2.4. Upgrade to this version or later.

Q: Is CVE-2026-54452 exploitable, and should I be worried?

Whether CVE-2026-54452 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-54452 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-54452?

Upgrade github.com/doyensec/safeurl to 0.2.4 or later.

Summary

safeurl is Missing IPv6 CIDR Ranges in Blocklist

The privateNetworks blocklist was found to be missing newly added CIDR ranges. More specifically, the following CIDR ranges were not being blocked:

64:ff9b:1::/48: NAT64 local-use prefix (RFC 8215)
5f00::/16: Segment Routing (SRv6) SIDs (RFC 9602)
3fff::/20: documentation prefix (RFC 9637)
100:0:0:1::/64: Dummy IPv6 Prefix (RFC 9780)

Workarounds

Disable IPv6 by setting EnableIPv6(false). This is the default behavior of the library.

Resolution

Upgrade to v0.2.4

Credits

safeurl thanks @tonghuaroot for reporting.

Impact

If exploited, an attacker would potentially be able to reach resources hosted on the IPs residing in the missing ranges.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Affected versions

github.com/doyensec/safeurl (< 0.2.4)

Security releases

github.com/doyensec/safeurl → 0.2.4 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/doyensec/safeurl to 0.2.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-54452? CVE-2026-54452 is a medium-severity server-side request forgery (SSRF) vulnerability in github.com/doyensec/safeurl (go), affecting versions < 0.2.4. It is fixed in 0.2.4. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
Which versions of github.com/doyensec/safeurl are affected by CVE-2026-54452? github.com/doyensec/safeurl (go) versions < 0.2.4 is affected.
Is there a fix for CVE-2026-54452? Yes. CVE-2026-54452 is fixed in 0.2.4. Upgrade to this version or later.
Is CVE-2026-54452 exploitable, and should I be worried? Whether CVE-2026-54452 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-54452 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-54452? Upgrade github.com/doyensec/safeurl to 0.2.4 or later.