CVE-2026-45033: CWE-696: Incorrect Behavior Order in github copilot-cli
GitHub Copilot CLI versions prior to 1.0.43 contain a high-severity vulnerability (CVE-2026-45033) that allows arbitrary code execution. This occurs when a malicious bare git repository is nested inside a project directory, exploiting git's automatic bare repository discovery during directory traversal. The vulnerability leverages git configuration keys such as core.fsmonitor and others that can execute arbitrary shell commands during normal git operations. This issue is fixed in version 1.0.43.
AI Analysis
Technical Summary
CVE-2026-45033 is a vulnerability in GitHub Copilot CLI before version 1.0.43 where a malicious bare git repository nested inside a project directory can cause arbitrary code execution. The root cause is git's automatic discovery of bare repositories during directory traversal, which allows an attacker to set executable config keys like core.fsmonitor, core.hookspath, diff.external, and merge.tool to arbitrary shell commands. These commands are executed by git during routine operations such as status, diff, or rev-parse without user awareness or approval. The vulnerability is classified under CWE-696 (Incorrect Behavior Order).
Potential Impact
An attacker who can place a malicious bare git repository inside a project directory can execute arbitrary code on the victim's system when the GitHub Copilot CLI performs git operations. This can lead to full compromise of the environment running the vulnerable CLI version. The CVSS 4.0 score is 8.5 (high severity), reflecting the local attack vector with low complexity but high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade GitHub Copilot CLI to version 1.0.43 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 1.0.43, applying this official fix is the recommended remediation. No other mitigation or temporary workaround is provided in the available data.
CVE-2026-45033: CWE-696: Incorrect Behavior Order in github copilot-cli
Description
GitHub Copilot CLI versions prior to 1.0.43 contain a high-severity vulnerability (CVE-2026-45033) that allows arbitrary code execution. This occurs when a malicious bare git repository is nested inside a project directory, exploiting git's automatic bare repository discovery during directory traversal. The vulnerability leverages git configuration keys such as core.fsmonitor and others that can execute arbitrary shell commands during normal git operations. This issue is fixed in version 1.0.43.
CVSS v4.0
Score 8.5high
Affected software
pkg:github/github/copilot-cliRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-45033 is a vulnerability in GitHub Copilot CLI before version 1.0.43 where a malicious bare git repository nested inside a project directory can cause arbitrary code execution. The root cause is git's automatic discovery of bare repositories during directory traversal, which allows an attacker to set executable config keys like core.fsmonitor, core.hookspath, diff.external, and merge.tool to arbitrary shell commands. These commands are executed by git during routine operations such as status, diff, or rev-parse without user awareness or approval. The vulnerability is classified under CWE-696 (Incorrect Behavior Order).
Potential Impact
An attacker who can place a malicious bare git repository inside a project directory can execute arbitrary code on the victim's system when the GitHub Copilot CLI performs git operations. This can lead to full compromise of the environment running the vulnerable CLI version. The CVSS 4.0 score is 8.5 (high severity), reflecting the local attack vector with low complexity but high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade GitHub Copilot CLI to version 1.0.43 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 1.0.43, applying this official fix is the recommended remediation. No other mitigation or temporary workaround is provided in the available data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-08T16:58:28.897Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a04a50ccbff5d8610e804c0
Added to database: 05/13/2026, 16:21:32 UTC
Last enriched: 05/20/2026, 19:10:52 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 111
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.