Symfony HttpFoundation: Malformed Paths Can Slip Past Access Rules

Published as "CVE-2025-64500: Incorrect parsing of PATH_INFO can lead to limited authorization bypass"

high Symfony Symfony components · Last reviewed Nov 8, 2026

CVE: CVE-2025-64500
GHSA: GHSA-3rg7-wf37-54rm
Packagist: PKSA-365x-2zjk-pt47
Reported: Nov 12, 2025

Lets an attacker reach some URLs that path-based access rules should block, in apps whose rules assume every path starts with a slash.

Affected and fixed versions

In 2 packages: symfony/http-foundation and symfony/symfony. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
6.4.0 – 6.4.28	6.4.29	Supported
5.4.0 – 5.4.49	5.4.50	Supported

Show 15 older branches, no longer supported

7.0.0 – 7.0.x	7.3.7
7.1.0 – 7.1.x	7.3.7
7.2.0 – 7.2.x	7.3.7
7.3.0 – 7.3.6	7.3.7
6.0.0 – 6.0.x	6.4.29
6.1.0 – 6.1.x	6.4.29
6.2.0 – 6.2.x	6.4.29
6.3.0 – 6.3.x	6.4.29
2.0.0 – 2.x	5.4.50
3.0.0 – 3.x	5.4.50
4.0.0 – 4.x	5.4.50
5.0.0 – 5.0.x	5.4.50
5.1.0 – 5.1.x	5.4.50
5.2.0 – 5.2.x	5.4.50
5.3.0 – 5.3.x	5.4.50

Upgrade

Run the line for the branch you are on. 1 other package listed above is affected too; update it the same way.

composer require symfony/http-foundation:^6.4.29
composer require symfony/http-foundation:^5.4.50

What this means

For some URLs, Symfony's Request class worked out a path that didn't start with /. Access rules written on the assumption that every path starts with a slash could then fail to match, letting an attacker reach pages those rules were meant to protect. The Symfony advisory calls it a limited authorization bypass.

Who is affected

Apps on an affected version of symfony/http-foundation, or of symfony/symfony, that make access decisions from the request path. Examples are access_control entries in security.yaml with patterns like ^/admin, and your own checks on $request->getPathInfo() that expect a leading /.

Checks that don't look at the path at all, such as #[IsGranted] on a controller or a voter, don't rely on that assumption.

What to do

Update symfony/http-foundation to the fixed release for your branch:

5.4: update to 5.4.50
6.4: update to 6.4.29
7.3: update to 7.3.7

The fix makes the request path always start with /.

Discovered by Andrew Atkinson and reported by Chris Smith.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Symfony HttpFoundation: Malformed Paths Can Slip Past Access Rules (CVE-2025-64500, GHSA-3rg7-wf37-54rm)
Details: https://phpnews.net/security/symfony/ghsa-3rg7-wf37-54rm

Affected versions, as Composer constraints:
- symfony/http-foundation, symfony/symfony: >=2.0.0,<3.0.0|>=3.0.0,<4.0.0|>=4.0.0,<5.0.0|>=5.0.0,<5.1.0|>=5.1.0,<5.2.0|>=5.2.0,<5.3.0|>=5.3.0,<5.4.0|>=5.4.0,<5.4.50|>=6.0.0,<6.1.0|>=6.1.0,<6.2.0|>=6.2.0,<6.3.0|>=6.3.0,<6.4.0|>=6.4.0,<6.4.29|>=7.0.0,<7.1.0|>=7.1.0,<7.2.0|>=7.2.0,<7.3.0|>=7.3.0,<7.3.7

Fixed releases on branches that still get security fixes:
- 6.4.0 – 6.4.28: update to 6.4.29
- 5.4.0 – 5.4.49: update to 5.4.50

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/symfony/ghsa-3rg7-wf37-54rm and check whether the project meets the conditions it describes (a feature in use, a config value, a driver) (if that page won't load, use https://github.com/advisories/GHSA-3rg7-wf37-54rm). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

← All Symfony advisories