Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 05 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zed
Zed zed |
|
| CPEs | cpe:2.3:a:zed:zed:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Zed
Zed zed |
Thu, 26 Feb 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 26 Feb 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zed-industries
Zed-industries zed |
|
| Vendors & Products |
Zed-industries
Zed-industries zed |
Thu, 26 Feb 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Zed Extension Sandbox Escape via Tar Symlink Following | |
| Weaknesses | CWE-61 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-27T04:55:52.466Z
Reserved: 2026-02-25T03:24:57.793Z
Link: CVE-2026-27976
Updated: 2026-02-26T16:54:05.876Z
Status : Analyzed
Published: 2026-02-26T00:16:27.293
Modified: 2026-03-05T16:08:38.163
Link: CVE-2026-27976
No data.
OpenCVE Enrichment
Updated: 2026-04-17T14:45:21Z