Summary
Description
The Request class improperly interprets some PATH_INFO in a way that leads to representing some URLs with a path that doesn't start with a /. This can allow bypassing some access control rules that are built with this /-prefix assumption.
Resolution
The Request class now ensures that URL paths always start with a /.
The patch for this issue is available here for branch 5.4.
Credits
We would like to thank Andrew Atkinson for discovering the issue, Chris Smith for reporting it and Nicolas Grekas for providing the fix.
Impact
CVE-2025-64500 has a CVSS score of 7.3 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.4.50, 6.4.29, 7.3.7); upgrading removes the vulnerable code path.
Affected versions
Security releases
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.
Remediation advice
symfony/http-foundation to 5.4.50 or later; symfony/http-foundation to 6.4.29 or later; symfony/http-foundation to 7.3.7 or later; symfony/symfony to 5.4.50 or later; symfony/symfony to 6.4.29 or later; symfony/symfony to 7.3.7 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-64500? CVE-2025-64500 is a high-severity security vulnerability in symfony/http-foundation (composer), affecting versions < 5.4.50. It is fixed in 5.4.50, 6.4.29, 7.3.7.
- How severe is CVE-2025-64500? CVE-2025-64500 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2025-64500?
symfony/http-foundation(composer) (versions < 5.4.50)symfony/symfony(composer) (versions >= 2.0.0, < 5.4.50)
- Is there a fix for CVE-2025-64500? Yes. CVE-2025-64500 is fixed in 5.4.50, 6.4.29, 7.3.7. Upgrade to this version or later.
- Is CVE-2025-64500 exploitable, and should I be worried? Whether CVE-2025-64500 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-2025-64500 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-2025-64500?
- Upgrade
symfony/http-foundationto 5.4.50 or later - Upgrade
symfony/http-foundationto 6.4.29 or later - Upgrade
symfony/http-foundationto 7.3.7 or later - Upgrade
symfony/symfonyto 5.4.50 or later - Upgrade
symfony/symfonyto 6.4.29 or later - Upgrade
symfony/symfonyto 7.3.7 or later
- Upgrade