HighGHSA-3rg7-wf37-54rmCVE-2025-64500

Symfony's incorrect parsing of PATH_INFO can lead to limited authorization bypass

Published 12 Nov 2025 · Updated 10 Sept 2026

Is your project on an affected symfony/http-foundation?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<5.4.50
Fixed in
5.4.50
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^5.4.50
Affected
>=6.0.0 <6.4.29
Fixed in
6.4.29
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^6.4.29
Affected
>=7.0.0 <7.3.7
Fixed in
7.3.7
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^7.3.7
Affected
>=2.0.0 <5.4.50
Fixed in
5.4.50
Update to the fixed version for your release line, for example:composer require symfony/symfony:^5.4.50
Affected
>=6.0.0 <6.4.29
Fixed in
6.4.29
Update to the fixed version for your release line, for example:composer require symfony/symfony:^6.4.29
Affected
>=7.0.0 <7.3.7
Fixed in
7.3.7
Update to the fixed version for your release line, for example:composer require symfony/symfony:^7.3.7

Details

Description

The Request class improperly interprets some PATH_INFO in a way that leads to representing some URLs with a path that doesn't start with a /. This can allow bypassing some access control rules that are built with this /-prefix assumption.

Resolution

The Request class now ensures that URL paths always start with a /.

The patch for this issue is available here for branch 5.4.

Credits

We would like to thank Andrew Atkinson for discovering the issue, Chris Smith for reporting it and Nicolas Grekas for providing the fix.

Is GHSA-3rg7-wf37-54rm in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected symfony/http-foundation, and gives you the command that fixes it.

More advisories for symfony/http-foundation

  • HighCVE-2026-108082Symfony: ReDoS in HeaderUtils::split() Reachable Through the Cache-Control Request Header · 27 Oct 2026
  • MediumCVE-2026-48736Symfony: IpUtils::PRIVATE_SUBNETS Omits IPv6 Transition Forms (6to4, NAT64, Teredo, IPv4-compatible): SSRF Bypass in NoPrivateNetworkHttpClient · 15 Jun 2026
  • LowCVE-2024-50345Symfony vulnerable to open redirect via browser-sanitized URLs · 6 Nov 2024
  • MediumCVE-2015-2309Symfony has unsafe methods in the Request class · 30 May 2024
  • MediumCVE-2014-6061Symfony has a security issue when parsing the Authorization header · 30 May 2024
  • HighCVE-2014-5244Symfony vulnerable to denial of service via a malicious HTTP Host header · 30 May 2024
All 15 advisories for symfony/http-foundation

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.