CVE-2025-64500 is a high-severity (CVSS 7.3) CWE-647 vulnerability in symfony/http-foundation. A fix is available for symfony/http-foundation — see the affected versions and patch details below.
Symfony's incorrect parsing of PATH_INFO can lead to limited authorization bypass
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64500.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-64500 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
symfony/http-foundation🐘symfony/http-foundation🐘symfony/http-foundation🐘symfony/symfony🐘symfony/symfony🐘symfony/symfonyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Symfony's HttpFoundation component defines an object-oriented layer for the HTTP specification. Starting in version 2.0.0 and prior to version 5.4.50, 6.4.29, and 7.3.7, 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. Starting in versions 5.4.50, 6.4.29, and 7.3.7, the Request class now ensures that URL paths always start with a /.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/http-foundation | all versions | 5.4.50composer require symfony/http-foundation:^5.4.50 |
| 🐘Packagist | symfony/http-foundation | ≥ 6.0.0&&< 6.4.29 | 6.4.29composer require symfony/http-foundation:^6.4.29 |
| 🐘Packagist | symfony/http-foundation | ≥ 7.0.0&&< 7.3.7 | 7.3.7composer require symfony/http-foundation:^7.3.7 |
| 🐘Packagist | symfony/symfony | ≥ 2.0.0&&< 5.4.50 | 5.4.50composer require symfony/symfony:^5.4.50 |
| 🐘Packagist | symfony/symfony | ≥ 6.0.0&&< 6.4.29 | 6.4.29composer require symfony/symfony:^6.4.29 |
| 🐘Packagist | symfony/symfony | ≥ 7.0.0&&< 7.3.7 | 7.3.7composer require symfony/symfony:^7.3.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/http-foundation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/http-foundation to 5.4.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64500 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-64500 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-64500. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2025-64500
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-64500 -u https://target- Template
- Symfony HttpFoundation - Access Control Bypass via PATH_INFO
- Severity
- high
- Impact
- Attackers can bypass access control rules, potentially gaining unauthorized access to restricted resources.
- Remediation
- Update to Symfony versions 5.4.50, 6.4.29, or 7.3.7 or later.
Template by ProjectDiscovery nuclei-templates (DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-64500 in your dependencies?
O3 Security finds CVE-2025-64500 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.