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.

The version of Symfony Process Component installed on the remote host is prior to 5.4.51, or 6.4.x prior to 6.4.33, or 7.3.x prior to 7.3.11, or 7.4.x prior to 7.4.5, or 8.0.x prior to 8.0.5. It is, therefore, affected by an argument injection vulnerability. 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 uses Symfony Process to invoke file-management commands 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.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number. Also note that this plugin does not distinguish between PHP packages installed via the OS package manager, PHP packages installed via Composer, or other sources. As a result, packages provided by your OS package repository may have backported fixes that this plugin may incorrectly report as vulnerable. Please refer to the OS-specific plugins for CVE-2026-24739 to check for backported fixes.

The version of Symfony installed on the remote host is prior to 5.4.51, or 6.4.x prior to 6.4.33, or 7.3.x prior to 7.3.11, or 7.4.x prior to 7.4.5, or 8.0.x prior to 8.0.5. It is, therefore, affected by an argument injection vulnerability in the Process component. 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 uses Symfony Process to invoke file-management commands 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.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number. Also note that this plugin does not distinguish between PHP packages installed via the OS package manager, PHP packages installed via Composer, or other sources. As a result, packages provided by your OS package repository may have backported fixes that this plugin may incorrectly report as vulnerable. Please refer to the OS-specific plugins for CVE-2026-24739 to check for backported fixes.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-24739)

ID	Name	Product	Family	Severity
298793	Symfony Process Component < 5.4.51 / 6.4.x < 6.4.33 / 7.3.x < 7.3.11 / 7.4.x < 7.4.5 / 8.0.x < 8.0.5 Argument Injection (GHSA-r39x-jcww-82v6)	Nessus	Misc.	medium
298792	Symfony < 5.4.51 / 6.4.x < 6.4.33 / 7.3.x < 7.3.11 / 7.4.x < 7.4.5 / 8.0.x < 8.0.5 Process Component Argument Injection (GHSA-r39x-jcww-82v6)	Nessus	Misc.	medium
437362	SCA: security update for symfony/process, symfony/symfony (GHSA-r39x-jcww-82v6)	Tenable Cloud Security	SCA Checks	medium
437362	SCA: security update for symfony/process, symfony/symfony (GHSA-r39x-jcww-82v6)	Tenable Self-Hosted Container Security	SCA Checks	medium

Detections

Analytics

CVE-2026-24739

medium

Tenable Plugins

medium

medium

medium

medium