GHSA-jxgr-3v7q-3w9v
LOWSymfony's `Security::login` does not take into account custom `user_checker`
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.
Blast Radius
symfony/security-bundle🐘symfony/security-bundle🐘symfony/security-bundle🐘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 custom user_checker defined on a firewall is not called when Login Programmaticaly with the Security::login method, leading to unwanted login.
Resolution
The Security::login method now ensure to call the configured user_checker.
The patch for this issue is available here for branch 6.4.
Credits
We would like to thank Oleg Andreyev, Antoine MAKDESSI for reporting the issue and Christian Flothmann for providing the fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/security-bundle | ≥ 6.2.0&&< 6.4.10 | 6.4.10 |
| 🐘Packagist | symfony/security-bundle | ≥ 7.0.0&&< 7.0.10 | 7.0.10 |
| 🐘Packagist | symfony/security-bundle | ≥ 7.1.0&&< 7.1.3 | 7.1.3 |
| 🐘Packagist | symfony/symfony | ≥ 6.2.0&&< 6.4.10 | 6.4.10 |
| 🐘Packagist | symfony/symfony | ≥ 7.0.0&&< 7.0.10 | 7.0.10 |
| 🐘Packagist | symfony/symfony | ≥ 7.1.0&&< 7.1.3 | 7.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-bundle. 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-bundle to 6.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxgr-3v7q-3w9v 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-jxgr-3v7q-3w9v 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-jxgr-3v7q-3w9v. 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-jxgr-3v7q-3w9v in your dependencies?
O3 detects GHSA-jxgr-3v7q-3w9v across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.