CVE-2026-25805
Zed ≤ 0.219.4
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-25805 is a medium-severity Product UI does not Warn User of Unsafe Actions (CWE-356) vulnerability in Zed Zed. Its CVSS base score is 6.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25805 affects Zed, a multiplayer code editor, in versions prior to 0.219.4. The vulnerability stems from the application's failure to display the parameters used when invoking tools, both at the time of requesting user allowance and afterward. This lack of visibility (classified under CWE-356) enables potentially unwanted or malicious parameter values to be executed without user awareness. The issue carries a CVSS v3.1 base score of 6.4 (AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
Exploitation requires network access, high privileges (such as those held by a collaborator in a multiplayer session), high attack complexity, and user interaction in the form of granting permission to the tool invocation. An attacker could craft a tool call with malicious parameters, tricking the user into approving it unknowingly, potentially leading to high-impact confidentiality, integrity, and availability violations on the victim's system.
The Zed project patched this in version 0.219.4 by adding expandable details for tool calls, enabling users to inspect parameters before and after invocation. Additional details are available in the GitHub Security Advisory at https://github.com/zed-industries/zed/security/advisories/GHSA-f2g4-87h6-4pxq.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6755
Vulnerability Data
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.…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mandates explicit user-visible indication, directly countering absence of warnings for device activation.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices include UI design requirements that warn users before unsafe actions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can verify presence of warnings for unsafe user actions.
Security awareness training can teach users to heed or demand warnings for unsafe actions.
Secure development life cycle requires UI design to warn users before unsafe actions.
Application security requirements include user warnings for dangerous operations.
Secure architecture principles can mandate confirmation prompts for risky actions.
Secure coding practices can embed user warnings before unsafe operations.