You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cortex XDR "parent_process_spoofing" kills the launching shell when Copilot CLI spawns git #5478
When starting copilot in a directory with a git repository, Cortex XDR kills cmd/powershell with a parent_process_spoofing when copilot runs git. i.e. copilot crashes the shell via Cortex.
Affected version
1.0.109
Steps to reproduce the behavior
git init in an empty folder.
Run copilot from cmd.exe or PowerShell.
Expected behavior
Copilot runs normally.
Additional context
Operating system: Windows 11, 10.0.26200
CPU architecture: x86_64 (AMD64), Intel Core i5-1345U
Terminal emulator: reproduces in both Windows Terminal and a standalone console window (conhost, launched from Explorer)
Shell: cmd.exe and PowerShell (Windows PowerShell 5.1 and PowerShell 7.6.9) both affected
Copilot CLI version: 1.0.109 (regression, started with 1.0.108)
Same issue here. Affected for about a week with Cortex XDR on Windows.
It always happens with Copilot CLI: ~2 seconds after starting copilot, the parent_process_spoofing rule fires and kills the parent process (the terminal window). Sometimes it also kills VS Code, so it may not be limited to the standalone CLI.
Version: GitHub Copilot CLI 1.0.111 and GitHub Copilot CLI 1.0.112
Terminal: PowerShell / cmd / Windows Terminal / VS Code terminal
Same issue. I can confirm that GitHub Copilot CLI 1.0.113 is also affected, tested from cmd.exe and pwsh.exe (PowerShell 7.x) in Windows Terminal. Worse, when Cortex blocks things, it seems to often impact other processes, too, when it kills terminal processes.
Note, I get the same Cortex alert and block regardless of whether GH Copilot is in a Git Repo. Creating an empty directory, changing to it, and running copilot.exe will reproduce the issue for me. The bit in the initial bug report about this being tied to starting copilot.exe in a git repo appears either wrong or things have gotten worse with the latest CLI release.
Activity
laeubi commentedon Nov 17, 2026
Also noticed this this morning on a Windows machine, this makes copilot cli effectively impossible to use.
arielkropp commentedon Nov 17, 2026
yes also experiencing this - basically unusable at this point
thorstenvogel commentedon Nov 17, 2026
also happens with Version v1.0.112 - unusable atm
asiercamara commentedon Nov 17, 2026
Same issue here. Affected for about a week with Cortex XDR on Windows.
It always happens with Copilot CLI: ~2 seconds after starting
copilot, theparent_process_spoofingrule fires and kills the parent process (the terminal window). Sometimes it also kills VS Code, so it may not be limited to the standalone CLI.Version: GitHub Copilot CLI 1.0.111 and GitHub Copilot CLI 1.0.112
Terminal: PowerShell / cmd / Windows Terminal / VS Code terminal
cashell commentedon Nov 18, 2026
Same issue. I can confirm that GitHub Copilot CLI
1.0.113is also affected, tested fromcmd.exeandpwsh.exe(PowerShell 7.x) in Windows Terminal. Worse, when Cortex blocks things, it seems to often impact other processes, too, when it kills terminal processes.Note, I get the same Cortex alert and block regardless of whether GH Copilot is in a Git Repo. Creating an empty directory, changing to it, and running
copilot.exewill reproduce the issue for me. The bit in the initial bug report about this being tied to startingcopilot.exein a git repo appears either wrong or things have gotten worse with the latest CLI release.