CVE-2026-27976
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS probability
- 0.49%
- CWE
- CWE-61
- Published
- 2026-02-25
- Last modified
- 2026-03-12
Affected products
- zed-industries zed
Weakness type
Related vulnerabilities
- CVE-2023-37460 — Plexus Archiver vulnerable to Arbitrary File Creation in AbstractUnArchiver
- CVE-2026-54420 — LiteSpeed cPanel plugin before 2.4.8 (as distributed in LiteSpeed WHM PlugIn before 5.3.2.0) mishandles symlinks provide
- CVE-2024-28189 — Judge0 vulnerable to Sandbox Escape Patch Bypass via chown running on Symbolic Link
- CVE-2024-28185 — Judge0 vulnerable to Sandbox Escape via Symbolic Link
- CVE-2025-68937 — Forgejo before 13.0.2 allows attackers to write to unintended files, and possibly obtain server shell access, because of
- CVE-2025-55345 — Unsafe symlink following in restricted workspace-write sandbox leads to RCE
- CVE-2024-54148 — Gogs has a Path Traversal in file editing UI
- CVE-2025-59343 — tar-fs has a symlink validation bypass if destination directory is predictable with a specific tarball