LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24739: Symfony has incorrect argument escaping under MSYS2/Git Bash on Windows that can lead to destructive file operations

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.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Symfony flaw affects Windows workflows using Git Bash or MSYS2. Symfony Process may pass a file path differently than intended, especially when the path contains “=”. In unlucky cases, cleanup or file-management tasks could delete or modify the wrong location. This is not broadly internet-exploitable, but it matters for developer machines and build automation.

Executive priority

Prioritize remediation for Windows-based developer and CI environments that run Symfony or Composer tooling under Git Bash/MSYS2. For Linux servers or Windows workflows using cmd.exe/PowerShell only, urgency is lower unless affected tooling is present.

Technical view

Symfony Process before 5.4.51, 6.4.33, 7.3.11, 7.4.5, and 8.0.5 mishandles escaping for MSYS2-sensitive characters on Windows. When PHP runs under MSYS2/Git Bash and spawns native Windows executables, argument conversion can corrupt or truncate arguments. The CVE maps to CWE-88 and has CVSS 6.3 with local attack vector and user interaction.

Likely exposure

Exposure is most likely in Windows developer, CI, or release environments running PHP/Symfony tooling from Git Bash or MSYS2. Risk increases where Symfony Process handles paths influenced by repositories, archives, temporary directories, or user-controlled configuration.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Exploitation requires a specific Windows MSYS2/Git Bash context and a process invocation where influenced arguments reach file-management operations. The main impact is integrity and availability, not confidentiality.

Researcher notes

The issue is environment-dependent and centers on argument escaping plus MSYS2 argument/path conversion. Validate exposure by combining version checks with runtime context. Do not assume all Symfony deployments are exploitable; the risky condition is Windows MSYS2/Git Bash spawning native executables through Symfony Process.

Mitigation direction

  • Upgrade Symfony to 5.4.51, 6.4.33, 7.3.11, 7.4.5, 8.0.5, or later.
  • Avoid running PHP tooling from Git Bash or MSYS2 on Windows.
  • Prefer cmd.exe or PowerShell for workflows spawning native Windows executables.
  • Avoid paths containing “=” or similar MSYS2-sensitive characters in affected workflows.
  • Review vendor guidance before using MSYS2 argument-conversion environment settings.

Validation and detection

  • Inventory Symfony versions in applications, Composer dependencies, and build tooling.
  • Identify Windows workflows running PHP from Git Bash or MSYS2.
  • Review Symfony Process usage that invokes file-management programs.
  • Check whether paths can be influenced by repositories, archives, temporary directories, or configuration.
  • Confirm upgraded patched versions are deployed where affected workflows exist.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-88: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24739 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.3CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H15.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2026-24739Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
symfonysymfony< 5.4.51, >= 6.4.0, < 6.4.33, >= 7.3.0, < 7.3.11, >= 7.4.0, < 7.4.5, >= 8.0.0 , < 8.0.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-88 · source CWE mapping

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.