CVE-2026-24739: Symfony has incorrect argument escaping under MSYS2/Git Bash on Windows that can lead to destructive file operations
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: symfony/process (Packagist) 6.4.33, 7.3.11, 7.4.5; symfony/symfony (Packagist) 6.4.33, 7.3.11, 7.4.5.
Low priority for now. Upgrade to symfony/process (Packagist) 6.4.33, 7.3.11, 7.4.5; symfony/symfony (Packagist) 6.4.33, 7.3.11, 7.4.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 28, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-88
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sensiolabs | symfony | cpe:2.3:a:sensiolabs:symfony |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sensiolabs symfonybefore 5.4.51
- sensiolabs symfony6.4.0 and later · before 6.4.33
- sensiolabs symfony7.3.0 and later · before 7.3.11
- sensiolabs symfony7.4.0 and later · before 7.4.5
- sensiolabs symfony8.0.0 and later · before 8.0.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
symfony symfony
- < 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.5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | symfony/process | from 6.4 · before 6.4.33 | 6.4.33 |
| Packagist | symfony/process | from 7.3 · before 7.3.11 | 7.3.11 |
| Packagist | symfony/process | from 7.4 · before 7.4.5 | 7.4.5 |
| Packagist | symfony/process | from 8.0 · before 8.0.5 | 8.0.5 |
| Packagist | symfony/process | before 5.4.51 | 5.4.51 |
| Packagist | symfony/symfony | from 6.4 · before 6.4.33 | 6.4.33 |
| Packagist | symfony/symfony | from 7.3 · before 7.3.11 | 7.3.11 |
| Packagist | symfony/symfony | from 7.4 · before 7.4.5 | 7.4.5 |
| Packagist | symfony/symfony | from 8.0 · before 8.0.5 | 8.0.5 |
| Packagist | symfony/symfony | before 5.4.51 | 5.4.51 |
Same product
sensiolabs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-18889An issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7.49Plan
- CVE-2018-14773An issue was discovered in Http Foundation in Symfony 2.7.0 through 2.7.48, 2.8.0 through 2.8.43, 3.3.0 through 3.3.17, 3.4.0 through 3.4.1343Plan
- CVE-2019-10910In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, when service ids allow user inp41Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-50345Nov 6, 2024 · Open redirect via browser-sanitized URLs in symfony/http-foundation24Monitor
- ← EarlierCVE-2024-51736Nov 6, 2024 · Command execution hijack on Windows with Process class in symfony/process39Monitor
- Later →CVE-2026-45065Jul 14, 2026 · Symfony: UrlGenerator Route-Requirement Bypass via Unanchored Regex Alternation → Off-Site //host URL Injection9Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:symfony/process | 5.4.51 | Package registry (OSV) |
| Packagist:symfony/process | 6.4.33 | Package registry (OSV) |
| Packagist:symfony/process | 7.3.11 | Package registry (OSV) |
| Packagist:symfony/process | 7.4.5 | Package registry (OSV) |
| Packagist:symfony/process | 8.0.5 | Package registry (OSV) |
| Packagist:symfony/symfony | 5.4.51 | Package registry (OSV) |
| Packagist:symfony/symfony | 6.4.33 | Package registry (OSV) |
| Packagist:symfony/symfony | 7.3.11 | Package registry (OSV) |
| Packagist:symfony/symfony | 7.4.5 | Package registry (OSV) |
| Packagist:symfony/symfony | 8.0.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-45068167 days apartSymfony: Argument Injection in SendmailTransport via Dash-Prefixed Recipient Address34Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Parameter InjectionCAPEC-137likelihood: Medium · Medium
- Flash Parameter InjectionCAPEC-174likelihood: High · Medium
- Using Meta-characters in E-mail Headers to Inject Malicious PayloadsCAPEC-41likelihood: High · High
- HTTP Parameter Pollution (HPP)CAPEC-460Medium
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.