GHSA-rfcf-m67m-jcrq is a medium-severity (CVSS 6.8) Improper Authentication vulnerability in symfony/security-http. O3 Security confirms whether GHSA-rfcf-m67m-jcrq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Authentication granted to all firewalls instead of just one
Real-World Exposure
symfony/security-http🐘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
When an application defines multiple firewalls, the authenticated token delivered by one of the firewalls is available to all other firewalls. This can be abused when the application defines different providers for different parts of an application. In such a situation, a user authenticated on one part of the application is considered authenticated on the whole application.
Resolution
We now ensure that the authenticated token is only available for the firewall that generates it.
The patch for this issue is available here for branch 5.3.
Credits
I would like to thank Bogdan, gndk, Paweł Warchoł, Warxcell, and Adrien Lamotte for reporting the issue and Wouter J for fixing the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/security-http | ≥ 5.3.0&&< 5.3.2 | 5.3.2 |
| 🐘Packagist | symfony/symfony | ≥ 5.3.0&&< 5.3.2 | 5.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-http. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update symfony/security-http to 5.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rfcf-m67m-jcrq 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 pinpoints whether GHSA-rfcf-m67m-jcrq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-rfcf-m67m-jcrq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rfcf-m67m-jcrq in your dependencies?
O3 detects GHSA-rfcf-m67m-jcrq across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.