Symfony Security::login() Skips the Firewall's Custom User Checker

Published as "CVE-2024-50341: Security::login does not take into account custom user_checker"

low Symfony Symfony components · Last reviewed Nov 10, 2026

CVE: CVE-2024-50341
GHSA: GHSA-jxgr-3v7q-3w9v
Packagist: PKSA-nzkq-gsnx-t6bw
Reported: Jul 17, 2024

Lets accounts a firewall's custom user_checker would reject log in anyway when the app logs them in with Security::login().

Affected and fixed versions

In 2 packages: symfony/security-bundle and symfony/symfony. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
6.4.0 – 6.4.9	6.4.10	Supported

Show 4 older branches, no longer supported

7.1.0 – 7.1.2	7.1.3
7.0.0 – 7.0.9	7.0.10
6.2.0 – 6.2.x	6.4.10
6.3.0 – 6.3.x	6.4.10

Upgrade

Run the line for the branch you are on. 1 other package listed above is affected too; update it the same way.

composer require symfony/security-bundle:^6.4.10

What this means

When your app logs a user in from code with Security::login(), Symfony skipped the custom user_checker you set on the firewall. An account that checker is meant to reject could still be logged in this way.

Apps often log users in from code after registration, a password reset or an email verification link. See the Symfony advisory and the fix.

Who is affected

Apps on symfony/security-bundle (also part of symfony/symfony) when both of these are true:

A firewall has a custom user_checker that rejects some users.
The app calls Security::login() for users that checker should be able to stop.

Apps without a custom user checker, or that never call Security::login(), aren't affected.

What to do

Update to 6.4.10, 7.0.10 or 7.1.3, depending on your branch. After the update, Security::login() calls the user checker configured on the firewall.

A later advisory found that this fix only ran the checker's checkPreAuth() method, not checkPostAuth(). See CVE-2026-123746 for the releases that fix both.

Reported by Oleg Andreyev and Antoine MAKDESSI. Christian Flothmann provided the fix.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Symfony Security::login() Skips the Firewall's Custom User Checker (CVE-2024-50341, GHSA-jxgr-3v7q-3w9v)
Details: https://phpnews.net/security/symfony/ghsa-jxgr-3v7q-3w9v

Affected versions, as Composer constraints:
- symfony/security-bundle, symfony/symfony: >=6.2.0,<6.3.0|>=6.3.0,<6.4.0|>=6.4.0,<6.4.10|>=7.0.0,<7.0.10|>=7.1.0,<7.1.3

Fixed releases on branches that still get security fixes:
- 6.4.0 – 6.4.9: update to 6.4.10

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/symfony/ghsa-jxgr-3v7q-3w9v and check whether the project meets the conditions it describes (a feature in use, a config value, a driver) (if that page won't load, use https://github.com/advisories/GHSA-jxgr-3v7q-3w9v). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

← All Symfony advisories