Code execution via unsanitized Git fsmonitor command
Published May 28, 2026 · Updated May 28, 2026
Command injection in Zed before 0.227.1 allows context-dependent attackers to execute code when a user opens a malicious repository. Zed invokes Git in the repository and permits its local .git/config core.fsmonitor value to be executed as a shell command without sanitization or restriction. Opening the folder is the required user interaction; the injected command runs with the Zed user's privileges and can read, alter, or delete accessible data.
Summary
What happened
Command injection in Zed before 0.227.1 allows context-dependent attackers to execute code when a user opens a malicious repository. Zed invokes Git in the repository and permits its local .git/config core.fsmonitor value to be executed as a shell command without sanitization or restriction. Opening the folder is the required user interaction; the injected command runs with the Zed user's privileges and can read, alter, or delete accessible data.
The record
- CVE
- CVE-2026-44465
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Zed Industries
- Product
- Zed
- Classifications
- CWE-78, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=< 0.227.1
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.
Weakness, pattern, technique
Public exploit references
- Poisoned core.fsmonitor repository proof of conceptproof 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