Skip to content
Fencer Vulns
medium 6.3

CVE-2026-24739 json

Symfony has incorrect argument escaping under MSYS2/Git Bash on Windows that can lead to destructive file operations

published 2026-01-28 9 mo ago modified 2026-09-10 1 mo ago also EUVD-2026-4873 , GHSA-r39x-jcww-82v6

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to versions 5.4.51, 6.4.33, 7.3.11, 7.4.5, and 8.0.5, the Symfony Process component did not correctly treat some characters (notably `=`) as “special” when escaping arguments on Windows. When PHP is executed from an MSYS2-based environment (e.g. Git Bash) and Symfony Process spawns native Windows executables, MSYS2’s argument/path conversion can mis-handle unquoted arguments containing these characters. This can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended. If an application (or tooling such as Composer scripts) uses Symfony Process to invoke file-management commands (e.g. `rmdir`, `del`, etc.) with a path argument containing `=`, the MSYS2 conversion layer may alter the argument at runtime. In affected setups this can result in operations being performed on an unintended path, up to and including deletion of the contents of a broader directory or drive. The issue is particularly relevant when untrusted input can influence process arguments (directly or indirectly, e.g. via repository paths, extracted archive paths, temporary directories, or user-controlled configuration). Versions 5.4.51, 6.4.33, 7.3.11, 7.4.5, and 8.0.5 contains a patch for the issue. Some workarounds are available. Avoid running PHP/one's own tooling from MSYS2-based shells on Windows; prefer cmd.exe or PowerShell for workflows that spawn native executables. Avoid passing paths containing `=` (and similar MSYS2-sensitive characters) to Symfony Process when operating under Git Bash/MSYS2. Where applicable, configure MSYS2 to disable or restrict argument conversion (e.g. via `MSYS2_ARG_CONV_EXCL`), understanding this may affect other tooling behavior.

Patch / fix

  • packagist symfony/process 5.4.51, 6.4.33, 7.3.11, 7.4.5, 8.0.5
  • packagist symfony/symfony 5.4.51, 6.4.33, 7.3.11, 7.4.5, 8.0.5
  • sensiolabs symfony 5.4.51, 6.4.33, 7.3.11, 7.4.5, 8.0.5

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-24739 updated cvss 6.3

symfony/symfony: symfony/process: Symfony argument escaping under MSYS2/Git Bash on Windows can lead to destructive file operations

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/symfony/symfony/issues/62921 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
GitHub 3.1 6.3 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist symfony/process
<5.4.51
>=6.4, <6.4.33
>=7.3, <7.3.11
>=7.4, <7.4.5
>=8.0, <8.0.5
5.4.51
6.4.33
7.3.11
7.4.5
8.0.5
packagist symfony/symfony
<5.4.51
>=6.4, <6.4.33
>=7.3, <7.3.11
>=7.4, <7.4.5
>=8.0, <8.0.5
5.4.51
6.4.33
7.3.11
7.4.5
8.0.5

Affected products

  • symfony symfony

Classification

Weakness
  • CWE-88 Improper Neutralization of Argument Delimiters in a Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.