Advisory record · GHSA-j5jh-hpr4-h332

Symfony Session Fixation Vulnerability

CVSS 3.1 LowEPSS 0.027 · 86th percentile

Published by the GitHub Advisory Database at 14 May 2022, 02:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
symfony/symfonyPackagist>=2.3.0, <2.3.35 || >=2.4.0, <2.6.12 || >=2.7.0, <2.7.72.3.35, 2.6.12, 2.7.7
symfony/security-httpPackagist>=2.4.0, <2.6.12 || >=2.7.0, <2.7.72.6.12, 2.7.7
symfony/securityPackagist>=2.3.0, <2.3.35 || >=2.4.0, <2.6.12 || >=2.7.0, <2.7.72.3.35, 2.6.12, 2.7.7
Identifiers
GHSA-j5jh-hpr4-h332 · CVE-2015-8124 · PKSA-3bc7-m4n7-t49v · PKSA-3kww-vzpv-5xn6 · PKSA-m51r-2nhf-3g41
Weakness (CWE)
CWE-384
Published
14 May 2022
Updated
16 Feb 2024

Machine-written summary

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

Symfony's symfony, symfony/security-http and symfony/security packages are affected in several version ranges, including before 2.3.35, 2.6.12 and 2.7.7. An attacker who already knows a victim's session id can impersonate that victim to the web application through the "Remember Me" login feature. Upgrade symfony/symfony, symfony/security-http and symfony/security to 2.3.35, 2.6.12 or 2.7.7, depending on your branch; no fix is listed for Symfony 2.4 or 2.5.

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:N/UI:R/S:U/C:L/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.027, the 86th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:32 UTC First seen by agentprime
  2. 31 Oct 2026, 14:32 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.