{"items":[{"id":"NVI-00004735","kind":"vulnerability","title":"Symfony's incorrect argument escaping under MSYS2/Git Bash can lead to destructive file operations on Windows","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-r39x-jcww-82v6","CVE-2026-24739"],"plain_summary":"OSV carries this publisher advisory for symfony/process, symfony/process, symfony/process, symfony/process, symfony/process. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.4.51 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.4.33 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.3.11 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.4.5 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.0.5 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.4.51 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.4.33 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.3.11 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.4.5 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.0.5 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-b1a00270e522d26751f2d71b390cca51"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T10:23:30.817Z","value":"6.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-bb8f5ff96f7ef9fbac572aa1bb875cb8"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.231%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.14005. Missing scores are unknown.","source_id":"sr-b1a00270e522d26751f2d71b390cca51"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-70f7a6f780cf65b8be9affb51a7fc247","url":"https://github.com/advisories/GHSA-r39x-jcww-82v6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r39x-jcww-82v6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.355Z"},{"id":"sr-bb8f5ff96f7ef9fbac572aa1bb875cb8","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-24739","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-24739","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:47.597Z"},{"id":"sr-b1a00270e522d26751f2d71b390cca51","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-24739","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.51"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 6.4; fixed 6.4.33"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.3; fixed 7.3.11"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.4; fixed 7.4.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 8.0; fixed 8.0.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.51"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 6.4; fixed 6.4.33"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.3; fixed 7.3.11"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.4; fixed 7.4.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 8.0; fixed 8.0.5"]}],"null_published_at":"2026-11-06T15:18:17.700Z","source_updated_at":"2026-09-10T03:50:59.252Z","source_disclosed_at":"2026-01-28T21:28:10.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:41.355Z"},{"id":"NVI-00004735","kind":"vulnerability","title":"Symfony's incorrect argument escaping under MSYS2/Git Bash can lead to destructive file operations on Windows","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-r39x-jcww-82v6","CVE-2026-24739"],"plain_summary":"OSV carries this publisher advisory for symfony/process, symfony/process, symfony/process, symfony/process, symfony/process. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.4.51 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.4.33 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.3.11 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.4.5 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.0.5 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.4.51 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.4.33 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.3.11 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.4.5 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.0.5 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-b1a00270e522d26751f2d71b390cca51"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.231%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.14005. Missing scores are unknown.","source_id":"sr-b1a00270e522d26751f2d71b390cca51"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-70f7a6f780cf65b8be9affb51a7fc247","url":"https://github.com/advisories/GHSA-r39x-jcww-82v6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r39x-jcww-82v6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.355Z"},{"id":"sr-b1a00270e522d26751f2d71b390cca51","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-24739","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.51"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 6.4; fixed 6.4.33"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.3; fixed 7.3.11"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.4; fixed 7.4.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 8.0; fixed 8.0.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.51"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 6.4; fixed 6.4.33"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.3; fixed 7.3.11"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.4; fixed 7.4.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 8.0; fixed 8.0.5"]}],"null_published_at":"2026-11-05T03:52:54.779Z","source_updated_at":"2026-09-10T03:50:59.252Z","source_disclosed_at":"2026-01-28T21:28:10.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:41.355Z"},{"id":"NVI-00004735","kind":"vulnerability","title":"Symfony's incorrect argument escaping under MSYS2/Git Bash can lead to destructive file operations on Windows","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-r39x-jcww-82v6","CVE-2026-24739"],"plain_summary":"OSV carries this publisher advisory for symfony/process, symfony/process, symfony/process, symfony/process, symfony/process. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.4.51 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.4.33 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.3.11 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.4.5 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.0.5 for symfony/process. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.4.51 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.4.33 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.3.11 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.4.5 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.0.5 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-70f7a6f780cf65b8be9affb51a7fc247","url":"https://github.com/advisories/GHSA-r39x-jcww-82v6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r39x-jcww-82v6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.355Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.51"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 6.4; fixed 6.4.33"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.3; fixed 7.3.11"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.4; fixed 7.4.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/process","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 8.0; fixed 8.0.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.51"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 6.4; fixed 6.4.33"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.3; fixed 7.3.11"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 7.4; fixed 7.4.5"]},{"certainty":"source_listed","source_ids":["sr-70f7a6f780cf65b8be9affb51a7fc247"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Summary\nThe 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 mishandle unquoted arguments containing these characters.\n\nThis can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended.\n\n### Impact\nIf 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.\n\nThe 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).\n\n### Resolution\nUpgrade to a Symfony release that includes the fix from symfony/sym","public_affected_ranges":["ECOSYSTEM: introduced 8.0; fixed 8.0.5"]}],"null_published_at":"2026-10-31T22:12:57.140Z","source_updated_at":"2026-09-10T03:50:59.252Z","source_disclosed_at":"2026-01-28T21:28:10.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:41.355Z"}],"next_cursor":null,"snapshot_revision":"42594"}