Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-123746

The Symfony Security HTTP componentAuthenticatorManager::authenticateU ...

Overview

Published
6 Nov 2026
Modified
10 Nov 2026
Low CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available
CVSS score Low, no score

Description

The Symfony Security HTTP component AuthenticatorManager::authenticateUser() does not run the firewall user checker’s checkPostAuth() method when a user is authenticated programmatically, allowing an account rejected by a custom user checker, such as an expired account, to be authenticated in Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.

AuthenticatorManager::authenticateUser() is used by UserAuthenticatorInterface::authenticateUser() and by the SecurityBundle’s Security::login() to authenticate a user programmatically, but it does not dispatch the security.authentication.success event, on which checkPostAuth() runs. The fix for CVE-2024-50341 made Security::login() call checkPreAuth(), but checkPostAuth() was still skipped. As a result, an account rejected by a custom user checker in checkPostAuth() is refused by form login and the other authenticators of the firewall, but can still be authenticated programmatically.

Applications are affected when they use a custom user checker that rejects users in checkPostAuth() and authenticate users programmatically, for example after a password reset or an e-mail verification link. A user whose account is rejected can then obtain an authenticated session through that flow. The default user checker does nothing in checkPostAuth(), so the default configuration is not affected.

The fix makes AuthenticatorManager::authenticateUser() dispatch the security.authentication.success event once the token is created and before it is stored, as authentications through the firewall do, so that checkPostAuth() runs and can reject the user.

Source: OX vulnerability database

Severity

LOW

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-288

Affected packages · 2

Packages affected by CVE-2026-123746
EcosystemPackageVulnerableFixed in
Composer (PHP) symfony/security-http >=5.4.0, <5.4.56>=6.3.0, <6.4.0>=6.4.0, <6.4.50>=7.2.0, <7.3.0>=8.0.0, <8.1.0+10 more No fix yet
Composer (PHP) symfony/symfony >=7.1.0, <7.2.0>=7.4.0, <7.4.23>=6.0.0, <6.1.0>=6.2.0, <6.3.0>=8.0.0, <8.1.0+10 more No fix yet

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

debian 4 releases · 1 package

affected 2 fixed 2
symfony
debian fixes for CVE-2026-123746
ReleasePackageFixed in
11 symfony affected
12 symfony affected
13 symfony 6.4.50+dfsg-0+deb13u1
14 symfony 7.4.23+dfsg-1

echo 1 release · 1 package

fixed 1
symfony
echo fixes for CVE-2026-123746
ReleasePackageFixed in
symfony 6.4.50+dfsg-0+deb13u1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.