Symfony Process on Windows: Git Bash Can Mangle Arguments and Hit Wrong Paths
Published as "Symfony's incorrect argument escaping under MSYS2/Git Bash can lead to destructive file operations on Windows"
- CVE
- CVE-2026-24739
- GHSA
- GHSA-r39x-jcww-82v6
- Packagist
- PKSA-rkkf-636k-qjb3
- Reported
- Jan 28, 2026
Can make file commands run through Symfony Process act on the wrong path, up to deleting a whole directory, when PHP runs from Git Bash.
Affected and fixed versions
In 2 packages: symfony/process 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 |
|---|---|---|
| 7.4 – 7.4.4 | 7.4.5 | Supported |
| 6.4 – 6.4.32 | 6.4.33 | Supported |
| Up to 5.4.50 | 5.4.51 | Supported |
Show 2 older branches, no longer supported
| 8.0 – 8.0.4 | 8.0.5 |
| 7.3 – 7.3.10 | 7.3.11 |
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/process:^7.4.5 composer require symfony/process:^6.4.33 composer require symfony/process:^5.4.51
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 Process on Windows: Git Bash Can Mangle Arguments and Hit Wrong Paths (CVE-2026-24739, GHSA-r39x-jcww-82v6) Details: https://phpnews.net/security/symfony/ghsa-r39x-jcww-82v6 Affected versions, as Composer constraints: - symfony/process, symfony/symfony: >=8.0,<8.0.5|>=7.4,<7.4.5|>=7.3,<7.3.11|>=6.4,<6.4.33|<5.4.51 Fixed releases on branches that still get security fixes: - 7.4 – 7.4.4: update to 7.4.5 - 6.4 – 6.4.32: update to 6.4.33 - Up to 5.4.50: update to 5.4.51 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 the project's advisory at https://github.com/advisories/GHSA-r39x-jcww-82v6 and check whether the project meets the conditions it describes. 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.