CVE-2024-50341 is a low-severity (CVSS 3.1) Improper Authentication vulnerability in symfony/security-bundle. A fix is available for symfony/security-bundle — see the affected versions and patch details below.
Security::login does not take into account custom user_checker in symfony/security-bundle
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-2024-50341.
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-2024-50341 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 378,156 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/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
symfony/security-bundle is a module for the Symphony PHP framework which provides a tight integration of the Security component into the Symfony full-stack framework. The custom user_checker defined on a firewall is not called when Login Programmaticaly with the Security::login method, leading to unwanted login. As of versions 6.4.10, 7.0.10 and 7.1.3 the Security::login method now ensure to call the configured user_checker. All users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/security-bundle | ≥ 6.2.0&&< 6.4.10 | 6.4.10composer require symfony/security-bundle:^6.4.10 |
| 🐘Packagist | symfony/security-bundle | ≥ 7.0.0&&< 7.0.10 | 7.0.10composer require symfony/security-bundle:^7.0.10 |
| 🐘Packagist | symfony/security-bundle | ≥ 7.1.0&&< 7.1.3 | 7.1.3composer require symfony/security-bundle:^7.1.3 |
| 🐘Packagist | symfony/symfony | ≥ 6.2.0&&< 6.4.10 | 6.4.10composer require symfony/symfony:^6.4.10 |
| 🐘Packagist | symfony/symfony | ≥ 7.0.0&&< 7.0.10 | 7.0.10composer require symfony/symfony:^7.0.10 |
| 🐘Packagist | symfony/symfony | ≥ 7.1.0&&< 7.1.3 | 7.1.3composer require symfony/symfony:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2024-50341 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-2024-50341 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-50341. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is CVE-2024-50341 in your dependencies?
O3 Security finds CVE-2024-50341 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.