Symfony HttpFoundation: Paths Glued to index.php Bypass Web Server Path Rules

Published as "Path Rules Enforced in Front of PHP Can Be Bypassed by Appending the Path to the Script Name"

low Symfony Symfony components · Last reviewed Nov 7, 2026

CVE: No CVE assigned
GHSA: None
Packagist: PKSA-pr6q-2w5s-kzzf
Reported: Nov 4, 2026

Lets requests get past nginx, Apache, CDN or WAF rules on a path like /admin, while Symfony still routes them to that path.

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
8.1.0 – 8.1.10	8.1.11	Supported
7.4.0 – 7.4.22	7.4.23	Supported
6.4.29 – 6.4.49	6.4.50	Supported
5.4.50 – 5.4.55	5.4.56	Supported

Show 2 older branches, no longer supported

8.0.0 – 8.0.x	8.1.11
7.3.7 – 7.3.x	7.4.23

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:^8.1.11
composer require symfony/http-foundation:^7.4.23
composer require symfony/http-foundation:^6.4.50
composer require symfony/http-foundation:^5.4.56

What this means

Symfony could route a request as if it were for a protected path like /admin when the path was appended straight onto the front controller's name (index.php), with no slash between them. Rules your web server, CDN or WAF enforce on /admin don't match that request, so it gets past them.

The behaviour came in with the fix for CVE-2025-64500, which is why only recent releases are affected. See the Symfony advisory and the fix.

Who is affected

Apps on an affected symfony/http-foundation version that block or restrict paths in front of PHP, for example:

a location /admin block in nginx
a <Location /admin> section in Apache
a CDN or WAF rule on a path

Rules Symfony enforces itself, access_control and firewalls, are not affected, because they read the same path as the router. If all your access rules live in Symfony, you're not exposed. Symfony rates the issue low.

The affected ranges start at 5.4.50, 6.4.29 and 7.3.7. Earlier releases on those branches don't have the bug.

What to do

Update symfony/http-foundation (or symfony/symfony) to 5.4.56, 6.4.50, 7.4.23 or 8.1.11, depending on your branch. There is no fixed 7.3 release, so apps on 7.3 need to move to 7.4.23.

Reported by Nicolas Grekas, with the fix by Jack Worman.

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: Paths Glued to index.php Bypass Web Server Path Rules (PKSA-PR6Q-2W5S-KZZF)
Details: https://phpnews.net/security/symfony/pksa-pr6q-2w5s-kzzf

Affected versions, as Composer constraints:
- symfony/http-foundation, symfony/symfony: >=5.4.50,<5.4.56|>=6.4.29,<6.4.50|>=7.3.7,<7.4.0|>=7.4.0,<7.4.23|>=8.0.0,<8.1.0|>=8.1.0,<8.1.11

Fixed releases on branches that still get security fixes:
- 8.1.0 – 8.1.10: update to 8.1.11
- 7.4.0 – 7.4.22: update to 7.4.23
- 6.4.29 – 6.4.49: update to 6.4.50
- 5.4.50 – 5.4.55: update to 5.4.56

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/pksa-pr6q-2w5s-kzzf and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). 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

The project's advisory →

← All Symfony advisories