Is symfony/process 3.1 vulnerable?

Composer · 11 releases from 3.1.0 to 3.1.10 · latest symfony/process is 8.1.10 · checked 1 Nov 2026

Yes: 2 known advisories

Yes. symfony/process 3.1.10, the last 3.1 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2024-51736, CVE-2026-24739. Upgrade to 5.4.51 or later to fix all of them.

Upgrade with:composer require symfony/process:^5.4.51

Is your project affected?

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

Advisories affecting symfony/process 3.1.10

  • MediumCVE-2026-24739GHSA-r39x-jcww-82v628 Jan 2026

    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
  • HighCVE-2024-51736GHSA-qq5c-677p-737q6 Nov 2024

    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

Which of your client projects are still on symfony/process 3.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact symfony/process version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other symfony/process versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.