GitHub Copilot CLI: Nested Bare Repository Can Execute Arbitrary Commands via core.fsmonitor
CVE-2026-45033 · GHSA-9ccr-r5hg-74gf · published 2026-05-11 · updated 2026-06-09
- Severity
- High
- CVSS score
- 7.8
- Chance of exploitation (EPSS)
- 0.35%
- Fixed in
- 1.0.43
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
An attacker who can place a malicious bare repository inside a project — for example, through: A pull request adding a directory that contains a bare repository A compromised or malicious dependency that includes a bare repository A cloned repository that already contains nested bare repositories — could achieve arbitrary code execution on the user's workstation whenever GitHub Copilot CLI performs git operations in or near the malicious directory. Successful exploitation could lead to data exfiltration, credential theft, file modification, or further system compromise.
Upgrade @github/copilot to 1.0.43 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The fix sets safe.bareRepository=explicit via git's GITCONFIGCOUNT / GITCONFIGKEY / GITCONFIGVALUE environment variable mechanism, which has the highest precedence over all config file sources. This prevents git from automatically discovering and using bare repositories during directory traversal — only explicitly allowlisted bare repositories will be used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @github/copilot | npm | <= 1.0.42 | 1.0.43 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.