GHSA-3fgc-wc43-9q2f: 
JavaScript vulnerability analysis and mitigation

Impact

TaskGraph spawns git, gh, claude and docker by bare name with the project directory as the working directory: packages/tm-core/src/common/utils/git-utils.ts (shell strings through exec/execSync), the claude --version probe in packages/tm-core/src/modules/ai/providers/claude-code.ts, and the Claude Code SDK's own spawn of claude. On Windows, cmd.exe and libuv's CreateProcess path search both look in the current directory before PATH unless the NoDefaultCurrentDirectoryInExePath environment variable is set. A repository that commits git.exe, git.cmd, claude.cmd or docker.cmd at its root therefore gets that file executed with the user's privileges the first time they run almost any taskgraph command (taskgraph list runs git for the branch name) or MCP tool in the clone. packages/tm-core/src/modules/setup/doctor.ts already sets the variable for its own spawns, so the hazard was only covered there. Windows only. All versions through 0.62.10.

Patches

The taskgraph binary and the MCP server set NoDefaultCurrentDirectoryInExePath=1 in their own environment at startup, which every spawn in the process and in the Claude Code SDK inherits, so bare-name spawns resolve through PATH only.

Workarounds

Set NoDefaultCurrentDirectoryInExePath=1 in your user environment, or check a clone's root for executables before running TaskGraph in it.