Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts repo with malicious .git/config core.fsmonitor
-
DeliveryPublishes repo on hosting platform or sends to victim
-
ExploitVictim clones and opens folder in vulnerable Zed
-
ExecutionZed's Git integration reads core.fsmonitor
-
PersistGit spawns attacker-specified command
-
ImpactArbitrary code runs as the developer user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The victim must open, in Zed prior to 0.227.1, a folder that contains an attacker-controlled .git/config file with the core.fsmonitor key set to an arbitrary command; user interaction (the Open Folder action) is required, but no authentication to Zed or any service is needed, and the vulnerability still fires when the folder is opened in Zed's untrusted mode - the documented safety boundary. Limiting factors: the attacker must deliver the malicious repository to the victim and convince them to open it (not merely clone or list it), and Git must be present/enabled for Zed's repo integration to activate. Platform is not restricted by the CPE wildcard, implying all OSes where Zed runs are in scope. |
| Impact | The CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H scores 8.6 because of scope change (the editor process executes attacker code) combined with full CIA impact, but the attack vector is Local and requires user interaction - the victim must open the malicious folder. There is no EPSS, KEV, or SSVC data provided, and no public exploit identified at time of analysis, so this is not currently confirmed actively exploited. Real-world risk is meaningful for developers who routinely clone and open untrusted repositories (security researchers, OSS triage, coding-challenge reviewers), but lower for users who only open vetted internal projects. The description explicitly states the bug fires in untrusted mode, which is the key risk multiplier - Zed's safety boundary is the failed control, not just an absence of one. |
| Exploit ScenarioDerived | An attacker publishes a repository (e.g., on GitHub, a package index, or a crafted ZIP attached to a bug report) containing a .git/config with core.fsmonitor set to an arbitrary command. A developer clones or downloads it and opens the folder in Zed - even using untrusted mode, expecting isolation - at which point Zed's Git integration invokes the fsmonitor command, executing the attacker's payload with the developer's privileges. No public exploit has been identified at time of analysis, but the technique is straightforward and well-understood. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 28, 2026
Remote code execution in Zed code editor versions prior to 0.227.1 occurs when a user opens a folder containing a malicious .git/config file that abuses the core.fsmonitor Git configuration option. The flaw triggers even in untrusted mode, defeating the safety boundary users expect when opening unknown repositories, and no public exploit has been identified at time of analysis though the advisory is published by the vendor.
RemediationAI
Vendor-released patch: upgrade Zed to 0.227.1 or later, per the GitHub Security Advisory at https://github.com/zed-industries/zed/security/advisories/GHSA-fj2r-rmw6-h222. Until the upgrade is rolled out, do not open untrusted repositories in Zed; if a folder must be inspected, clone it on a sandboxed host or first remove or audit the .git/config file (specifically any core.fsmonitor, core.sshCommand, or other command-invoking keys) before opening. Restricting Zed to opening only directories from known-trusted sources is the most practical compensating control, with the trade-off that it interrupts normal triage of unknown OSS repositories.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Zed is a Rust-based collaborative code editor developed by Zed Industries (CPE: cpe:2.3:a:zed-industries:zed). The vulnerability is rooted in CWE-78 (OS Command Injection) and abuses Git's core.fsmonitor option, which lets Git invoke an external file system monitor command to track changed files. When Zed opens a directory and initializes its Git integration, it honors per-repository .git/config values including core.fsmonitor, causing Git (invoked under Zed) to execute the attacker-supplied program. This is a well-known Git misuse class - similar fsmonitor abuse has historically affected other editors that auto-load repository configuration without first vetting it against a trusted scope.
Know when Zed gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
1DescriptionGitHub Advisory
Zed is a code editor. Prior to 0.227.1, Zed IDE executes arbitrary commands when opening a folder with a malicious .git/config file that abuses the core.fsmonitor Git configuration option. This allows an attacker to achieve Remote Code Execution (RCE) when a victim open a folder in untrusted mode. This vulnerability is fixed in 0.227.1.
Executive ViewAI
Zed code editor versions before 0.227.1 contain a remote code execution vulnerability triggered by opening folders with malicious Git configuration files, bypassing the editor's safety mechanisms for untrusted repositories. Development teams using affected versions face immediate risk of supply chain compromise and endpoint exploitation when interacting with external code; no public exploit has been identified at time of analysis. Immediate patching is critical to restore the security boundary developers rely on when navigating untrusted codebases.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Zed, a code editor, has an extension installer allows tar/gzip downloads. [CVSS 8.8 HIGH]
Zed code editor versions prior to 0.224.4 contain a path traversal vulnerability in ZIP extraction that fails to sanitiz
Arbitrary code execution in the Zed code editor affects all versions prior to 0.218.2-pre, where Model Context Protocol
Arbitrary code execution in the Zed code editor (all versions prior to 0.218.2-pre) lets a project's .zed/settings.json
Zed code editor versions before 0.225.9 fail to properly validate symbolic links in Agent file tools, allowing attackers
Zed Editor versions prior to 0.219.4 fail to display tool invocation parameters during permission prompts or after execu
A directory traversal vulnerability with remote code execution in Prim'X Zed!. Rated critical severity (CVSS 9.8), this
Arbitrary code execution in the Zed code editor (versions prior to 0.229.0) is possible by abusing its terminal tool per
Command injection in Zed code editor versions prior to 0.229.0 allows bypass of the terminal tool's permission allowlist
Remote command execution in Zed code editor versions prior to 0.227.1 occurs when opening SSH or WSL remote terminals be
By default, .ZED containers produced by PRIMX ZED!. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
We are tasked to synthesize data from multiple intelligence sources about CVE-2026-44462 into a comprehensive JSON analy
EUVD-2026-32937
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB