Vulnerability in @github/copilot (CVE-2026-45033)
Summary
Vulnerability in @github/copilot (CVE-2026-45033). Successful exploitation can lead to full system takeover. Exploitable via core.fsmonitor. Mitigation: upgrade to 1.0.43 or later.
Original description
The description as published by the source.
GitHub Copilot CLI brings AI-powered coding assistance directly to your command line. Prior to 1.0.43, a security vulnerability has been identified in GitHub Copilot CLI where a malicious bare git repository nested inside a project directory can achieve arbitrary code execution when the agent performs git operations. By exploiting git's automatic bare repository discovery during directory traversal, an attacker can set core.fsmonitor or other executable config keys to run arbitrary commands without user awareness or approval. The vulnerability arises because git's core.fsmonitor config key (and 15+ similar keys such as core.hookspath, diff.external, merge.tool, etc.) can specify arbitrary shell commands that git will execute as part of normal operations like status, diff, or rev-parse. This vulnerability is fixed in 1.0.43.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45033 has been found in @github/copilot.
Attackers can target a specific entry point like core.fsmonitor over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade @github/copilot to 1.0.43 or later.
If unsure, ask your IT team or search "@github/copilot CVE-2026-45033" on the vendor's site.
CVE-2026-45033 (@github/copilot) — CWE-696 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: core.fsmonitor / core.hookspath / diff.external / merge.tool
Patched: 1.0.43 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-696) exists in @github/copilot. Attackers reach the vulnerable code path via core.fsmonitor.
Check the vendor advisory for the affected versions of @github/copilot. Attack surface: core.fsmonitor / core.hookspath / diff.external / merge.tool.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 1.0.43.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@github/copilot' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@github/copilot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@github/copilotを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @github/copilot to 1.0.43ステージング環境で 1.0.43 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com