CVE-2025-68433: zed · Command Injection
Affects zedSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubzed-industries/zedpkg:github/zed-industries/zedOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-68433, European organizations should: 1) Immediately upgrade all Zed IDE installations to version 0.218.2-pre or later, which includes the worktree trust mechanism to prevent automatic execution of untrusted MCP configurations. 2) Implement strict policies to restrict opening projects only from trusted sources and verified repositories. 3) Enforce code review and scanning of .zed/settings.json files before opening projects, using automated tools or manual inspection to detect suspicious shell commands. 4) Educate developers about the risks of opening untrusted projects and the importance of verifying project configuration files. 5) Use endpoint protection solutions capable of detecting anomalous shell command executions initiated by the IDE process. 6) Consider running the IDE in a sandboxed or containerized environment to limit the impact of potential exploitation. 7) Monitor logs and system behavior for unusual activity following project openings. 8) Maintain an inventory of development tools and versions to ensure timely patching. These measures go beyond generic advice by focusing on procedural controls, developer awareness, and environment hardening specific to this vulnerability’s exploitation vector.
Description
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.