Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:NSummary
CVE-2026-27800 is a high-severity Path Traversal (CWE-22) vulnerability in Zed Zed. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
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-27800 is a Zip Slip path traversal vulnerability in the Zed code editor, affecting versions prior to 0.224.4. The issue resides in the `extract_zip()` function within `crates/util/src/archive.rs`, which does not properly validate ZIP entry filenames against path traversal sequences such as `../`. This flaw enables malicious ZIP archives to extract files beyond the intended sandbox directory for extensions. The vulnerability is rated 7.4 on the CVSS 3.1 scale (AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N) and maps to CWE-22.
An attacker can exploit this vulnerability by crafting a malicious ZIP archive disguised as a legitimate Zed extension. Users must be tricked into downloading and installing the extension via user interaction, such as clicking a link from an untrusted source. Successful exploitation allows the attacker to write arbitrary files outside the extension's sandbox, potentially overwriting critical files and leading to integrity violations like configuration changes or persistence mechanisms, though no direct confidentiality or availability impacts are noted.
The official Zed security advisory at https://github.com/zed-industries/zed/security/advisories/GHSA-v385-xh3h-rrfr details the issue and confirms that upgrading to version 0.224.4 resolves the vulnerability by implementing proper path validation during ZIP extraction. Security practitioners should advise users to update Zed immediately and avoid installing extensions from untrusted sources.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8773
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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 in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.