Code execution via nested bare repository configuration
Published May 13, 2026 · Updated May 13, 2026
Code execution in GitHub Copilot CLI before 1.0.43 allows local users to run arbitrary commands through a malicious nested bare repository. Git automatically discovers the bare repository and executes core.fsmonitor or similar command-bearing configuration during routine operations. Reachability requires attacker-controlled repository content and a Git operation; execution can expose credentials, modify files, or compromise the workstation.
Summary
What happened
Code execution in GitHub Copilot CLI before 1.0.43 allows local users to run arbitrary commands through a malicious nested bare repository. Git automatically discovers the bare repository and executes core.fsmonitor or similar command-bearing configuration during routine operations. Reachability requires attacker-controlled repository content and a Git operation; execution can expose credentials, modify files, or compromise the workstation.
The record
- CVE
- CVE-2026-45033
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- Product
- GitHub Copilot CLI
- Classifications
- CWE-696, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.43
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Nested bare repository attack scenarioproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo