Zed, a code editor, contains an OS command injection vulnerability (CVE-2026-44466) in versions prior to 0.229.0. The issue arises because the terminal tool permission system can be bypassed using bash arithmetic expansion $((... )), allowing execution of arbitrary commands nested inside an allowlisted command such as echo. This vulnerability has a high severity with a CVSS score of 8.6. The vulnerability is fixed in version 0.229.0.
Zed code editor versions prior to 0.229.0 contain a vulnerability in the terminal tool permission system that allows bypass by prepending environment variable assignments to allowlisted commands. This can hijack program behavior, such as the PAGER environment variable, to execute arbitrary code. The issue is addressed in version 0.229.0. The vulnerability has a high severity score of 8.6 and impacts confidentiality, integrity, and availability. No known exploits in the wild have been reported.
Zed, a code editor, had a vulnerability in versions prior to 0.229.0 where its terminal tool permission system could be bypassed using bash variable expansion chaining (${var@P}). This allowed arbitrary command execution under an allowlisted command prefix. The issue is classified under CWE-184 (Incomplete List of Disallowed Inputs). The vulnerability has a CVSS score of 6.4, indicating medium severity. A fix for this vulnerability was introduced in version 0.229.0.
Zed IDE versions prior to 0.227.1 contain a vulnerability where opening a folder with a specially crafted . git/config file can lead to remote code execution. This occurs due to improper neutralization of special elements in OS commands related to the core.fsmonitor Git configuration option. The vulnerability is fixed in version 0.227.1.
Zed code editor versions prior to 0.227.1 contain an OS command injection vulnerability due to improper neutralization of special elements in environment variable keys used in remote SSH/WSL command construction. An attacker able to control environment variable keys can inject shell expansions that execute arbitrary commands on the remote host under the victim user's account. This vulnerability is addressed in version 0.227.1.
Zed, a code editor, has an extension installer allows tar/gzip downloads. Prior to version 0.224.4, the tar extractor (`async_tar::Archive::unpack`) creates symlinks from the archive without validation, and the path guard (`writeable_path_from_extension`) only performs lexical prefix checks without resolving symlinks. An attacker can ship a tar that first creates a symlink inside the extension workdir pointing outside (e.g., `escape -> /`), then writes files through the symlink, causing writes to arbitrary host paths. This escapes the extension sandbox and enables code execution. Version 0.224.4 patches the issue.
Zed, a code editor, has a symlink escape vulnerability in versions prior to 0.225.9 in Agent file tools (`read_file`, `edit_file`). It allows reading and writing files **outside the project directory** when a project contains symbolic links pointing to external paths. This bypasses the intended workspace boundary and privacy protections (`file_scan_exclusions`, `private_files`), potentially leaking sensitive user data to the LLM. Version 0.225.9 fixes the issue.
Zed, a code editor, has a Zip Slip (Path Traversal) vulnerability exists in its extension archive extraction functionality prior to version 0.224.4. The `extract_zip()` function in `crates/util/src/archive.rs` fails to validate ZIP entry filenames for path traversal sequences (e.g., `../`). This allows a malicious extension to write files outside its designated sandbox directory by downloading and extracting a crafted ZIP archive. Version 0.224.4 fixes the issue.
Zed is a multiplayer code editor. Prior to 0.219.4, Zed does not show with which parameters a tool is being invoked, when asking for allowance. Further it does not show after the tool was being invoked, which parameters were used. Thus, maybe unwanted or even malicious values could be used without the user having a chance to notice it. Patched in Zed Editor 0.219.4 which includes expandable tool call details.
Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.
Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.
Zed is a multiplayer code editor. Prior to version 0.197.3, in the Zed Agent Panel allowed for an AI agent to achieve Remote Code Execution (RCE) by bypassing user permission checks. An AI Agent could have exploited a permissions bypass vulnerability to create or modify a project-specific configuration file, leading to the execution of arbitrary commands on a victim's machine without the explicit approval that would otherwise be required. This vulnerability has been patched in version 0.197.3. A workaround for this issue involves either avoid sending prompts to the Agent Panel, or to limit the AI Agent's file system access.