Symfony's incorrect parsing of PATH_INFO can lead to limited authorization bypassGHSA-3rg7-wf37-54rm
HIGHFix: symfony/symfony@9962b91GHSA-3rg7-wf37-54rm 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.
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 GHSA-3rg7-wf37-54rm.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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
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.
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 |
Affected Products
httpfoundationsensiolabssymfonysensiolabsDetection & 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 GHSA-3rg7-wf37-54rm is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
How to detect GHSA-3rg7-wf37-54rm
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-3rg7-wf37-54rm -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 GHSA-3rg7-wf37-54rm in your dependencies?
Find it across Packagist, including transitive dependencies.