Advisory record · GHSA-jxgr-3v7q-3w9v

Symfony's `Security::login` does not take into account custom `user_checker`

CVSS 3.1 LowEPSS 0.0031 · 24th percentile

Published by the GitHub Advisory Database at 6 Nov 2024, 15:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
symfony/security-bundlePackagist>=6.2.0, <6.4.10 || >=7.0.0, <7.0.10 || >=7.1.0, <7.1.36.4.10, 7.0.10, 7.1.3
symfony/symfonyPackagist>=6.2.0, <6.4.10 || >=7.0.0, <7.0.10 || >=7.1.0, <7.1.36.4.10, 7.0.10, 7.1.3
Identifiers
GHSA-jxgr-3v7q-3w9v · CVE-2024-50341 · PKSA-nmpz-hw89-qbtt · PKSA-nzkq-gsnx-t6bw
Weakness (CWE)
CWE-287
Published
6 Nov 2024
Updated
7 Nov 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Symfony's symfony/security-bundle and symfony/symfony packages, versions from 6.2.0 before 6.4.10, from 7.0.0 before 7.0.10, and from 7.1.0 before 7.1.3, are affected. When code calls the Security::login method to log a user in programmatically, the custom user_checker configured on the firewall is not run, which can allow a login that the checker would have blocked. The source gives few details about who can trigger this or what the impact is. Upgrade to 6.4.10, 7.0.10, or 7.1.3, depending on your branch.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
3.1 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 24th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:29 UTC First seen by agentprime
  2. 31 Oct 2026, 14:29 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.