GHSA-g97c-jfx6-xvxh: symfony/symfony (CVE-2015-8125)

Package	Ecosystem	Affected	Fixed in
symfony/symfony	Packagist	>=2.3.0, <2.3.35 \|\| >=2.7.0, <2.7.7 \|\| >=2.4.0, <2.6.12	2.3.35, 2.7.7, 2.6.12
symfony/form	Packagist	>=2.3.0, <2.3.35 \|\| >=2.4.0, <2.6.12 \|\| >=2.7.0, <2.7.7	2.3.35, 2.6.12, 2.7.7
symfony/security-http	Packagist	>=2.4.0, <2.6.12 \|\| >=2.7.0, <2.7.7	2.6.12, 2.7.7
symfony/security	Packagist	>=2.3.0, <2.3.35 \|\| >=2.4.0, <2.6.12 \|\| >=2.7.0, <2.7.7	2.3.35, 2.6.12, 2.7.7

Machine-written summary

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

Symfony's symfony/symfony, symfony/form, symfony/security and symfony/security-http packages are affected in versions 2.3.0 before 2.3.35, 2.4.0 before 2.6.12, and 2.7.0 before 2.7.7 (security-http is affected only from 2.4.0). A remote attacker may be able to carry out a timing attack against remember-me, digest authentication, or legacy CSRF token checks, with unspecified impact. The source gives few details. Upgrade to 2.3.35, 2.6.12, or 2.7.7, 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

No source has published a CVSS score for this record yet.

CISA KEV Not listed.
EPSS 0.025, the 85th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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