symfony/process vulnerabilities
Executes commands in sub-processes
- Registry
- Composer
- Latest
- 8.1.10
- License
- MIT
2 known advisories
The latest version, 8.1.10, is not affected by any of them. Projects on older versions may be.
composer require symfony/process:^8.1.10Is your project on an affected symfony/process?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for symfony/process
Symfony's incorrect argument escaping under MSYS2/Git Bash can lead to destructive file operations on Windows
- Affected
- <5.4.51 · >=6.4 <6.4.33 · >=7.3 <7.3.11 · >=7.4 <7.4.5 · >=8.0 <8.0.5
- Fixed in
- 5.4.51, 6.4.33, 7.3.11, 7.4.5, 8.0.5
Symfony vulnerable to command execution hijack on Windows with Process class
- Affected
- <5.4.46 · >=6.0.0 <6.4.14 · >=7.0.0 <7.1.7
- Fixed in
- 5.4.46, 6.4.14, 7.1.7
Is your symfony/process version vulnerable?
- symfony/process 8.1No known advisories in 8.1.10
- symfony/process 8.0No known advisories in 8.0.13
- symfony/process 7.4No known advisories in 7.4.22
- symfony/process 7.3No known advisories in 7.3.11
- symfony/process 7.2No known advisories in 7.2.9
- symfony/process 7.1No known advisories in 7.1.8
- symfony/process 7.01 advisory in 7.0.8
- symfony/process 6.4No known advisories in 6.4.49
- symfony/process 6.31 advisory in 6.3.12
- symfony/process 6.21 advisory in 6.2.13
- symfony/process 6.11 advisory in 6.1.11
- symfony/process 6.01 advisory in 6.0.19
Which of your client projects still run an old symfony/process?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.