Server-side Request Forgery (SSRF) Affecting symfony/symfony package, versions <5.4.53>=6.0.0-BETA1, <6.4.41>=7.0.0-BETA1, <7.4.13>=8.0.0-BETA1, <8.0.13
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PHP-SYMFONYSYMFONY-16894768
- published27 May 2026
- disclosed27 May 2026
- credittonghuaroot
Introduced: 27 May 2026
CVE-2026-48736 (opens in a new tab)How to fix?
Upgrade symfony/symfony to version 5.4.53, 6.4.41, 7.4.13, 8.0.13 or higher.
Overview
symfony/symfony is a PHP framework for web applications and a set of reusable PHP components.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF). The NoPrivateNetworkHttpClient is designed to be a security boundary that blocks requests to private/internal networks. Because IpUtils::PRIVATE_SUBNETS fails to account for IPv6 transition forms (like 6to4, Teredo, or NAT64), an attacker supplying a specially crafted URL (e.g., http://[2002:7f00:1::]/ which resolves to 127.0.0.1) can bypass the security mechanism. This allows the application to be tricked into making unintended HTTP requests to internal IP addresses (SSRF).