CVE-2026-25805: CWE-356: Product UI does not Warn User of Unsafe Actions in zed-industries zed
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.
AI Analysis
Technical Summary
CVE-2026-25805 is a vulnerability classified under CWE-356, which concerns the lack of adequate user interface warnings for unsafe actions. The affected product, Zed, is a multiplayer code editor used for collaborative software development. Prior to version 0.219.4, Zed's UI does not display the parameters with which a tool is invoked when requesting user permission, nor does it show these parameters after the tool has been executed. This omission means users cannot verify or detect if malicious or unintended parameters are being used during tool execution. Such a flaw can be exploited by an attacker with privileges and requiring user interaction to trick users into approving unsafe tool invocations, potentially leading to unauthorized code execution, data leakage, or system compromise. The vulnerability has a CVSS v3.1 base score of 6.4, reflecting a medium severity with network attack vector, high attack complexity, required privileges, and user interaction. The scope is unchanged, but the impact on confidentiality, integrity, and availability is high. The vendor addressed this issue in Zed version 0.219.4 by introducing expandable tool call details in the UI, improving transparency and allowing users to see exactly what parameters are being used during tool invocation. No known exploits are currently reported in the wild.
Potential Impact
For European organizations, especially those involved in software development and collaborative coding environments, this vulnerability poses a risk of unauthorized code execution or injection of malicious parameters during tool invocation in Zed. This can lead to data breaches, intellectual property theft, or disruption of development workflows. Given the collaborative nature of Zed, compromised parameters could propagate malicious code or configurations across teams, amplifying the impact. Confidentiality, integrity, and availability of development environments and source code repositories could be severely affected. The requirement for user interaction and privileges limits the attack surface but does not eliminate risk, particularly in environments with less stringent access controls or where social engineering is feasible. Organizations relying on Zed without the patched version may face increased risk of insider threats or targeted attacks exploiting this UI weakness.
Mitigation Recommendations
European organizations should immediately upgrade all instances of Zed to version 0.219.4 or later to benefit from the patched UI that displays tool invocation parameters. Until upgrades are complete, enforce strict policies requiring manual verification of all tool invocations and parameters in collaborative sessions. Implement role-based access controls to limit privileges for tool execution within Zed. Conduct user training to raise awareness about the risks of approving tool actions without verifying parameters. Employ network segmentation and monitoring to detect anomalous tool usage or unexpected parameter patterns. Integrate code review and automated scanning tools to detect suspicious code or parameter injections. Maintain an inventory of all Zed installations and monitor for unauthorized versions. Finally, consider isolating critical development environments from internet access to reduce exposure.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden
CVE-2026-25805: CWE-356: Product UI does not Warn User of Unsafe Actions in zed-industries zed
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2026-25805 is a vulnerability classified under CWE-356, which concerns the lack of adequate user interface warnings for unsafe actions. The affected product, Zed, is a multiplayer code editor used for collaborative software development. Prior to version 0.219.4, Zed's UI does not display the parameters with which a tool is invoked when requesting user permission, nor does it show these parameters after the tool has been executed. This omission means users cannot verify or detect if malicious or unintended parameters are being used during tool execution. Such a flaw can be exploited by an attacker with privileges and requiring user interaction to trick users into approving unsafe tool invocations, potentially leading to unauthorized code execution, data leakage, or system compromise. The vulnerability has a CVSS v3.1 base score of 6.4, reflecting a medium severity with network attack vector, high attack complexity, required privileges, and user interaction. The scope is unchanged, but the impact on confidentiality, integrity, and availability is high. The vendor addressed this issue in Zed version 0.219.4 by introducing expandable tool call details in the UI, improving transparency and allowing users to see exactly what parameters are being used during tool invocation. No known exploits are currently reported in the wild.
Potential Impact
For European organizations, especially those involved in software development and collaborative coding environments, this vulnerability poses a risk of unauthorized code execution or injection of malicious parameters during tool invocation in Zed. This can lead to data breaches, intellectual property theft, or disruption of development workflows. Given the collaborative nature of Zed, compromised parameters could propagate malicious code or configurations across teams, amplifying the impact. Confidentiality, integrity, and availability of development environments and source code repositories could be severely affected. The requirement for user interaction and privileges limits the attack surface but does not eliminate risk, particularly in environments with less stringent access controls or where social engineering is feasible. Organizations relying on Zed without the patched version may face increased risk of insider threats or targeted attacks exploiting this UI weakness.
Mitigation Recommendations
European organizations should immediately upgrade all instances of Zed to version 0.219.4 or later to benefit from the patched UI that displays tool invocation parameters. Until upgrades are complete, enforce strict policies requiring manual verification of all tool invocations and parameters in collaborative sessions. Implement role-based access controls to limit privileges for tool execution within Zed. Conduct user training to raise awareness about the risks of approving tool actions without verifying parameters. Employ network segmentation and monitoring to detect anomalous tool usage or unexpected parameter patterns. Integrate code review and automated scanning tools to detect suspicious code or parameter injections. Maintain an inventory of all Zed installations and monitor for unauthorized versions. Finally, consider isolating critical development environments from internet access to reduce exposure.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-05T19:58:01.641Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 698b6f014b57a58fa11d3753
Added to database: 2/10/2026, 5:46:41 PM
Last enriched: 2/10/2026, 6:01:14 PM
Last updated: 2/21/2026, 12:18:54 AM
Views: 29
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.