{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27976 exists.","fix":"No fix has been published for CVE-2026-27976 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27976 is a high-severity path traversal vulnerability in zed-industries zed, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-27976 and fix it if it is affected.\n\nWhat it is: CVE-2026-27976 is a high-severity path traversal vulnerability in zed-industries zed, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27976 exists.\n\nAffected product: zed-industries zed. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27976/ (Markdown: https://insights.sbomify.com/CVE-2026-27976/index.md)","id":"CVE-2026-27976","markdown":"https://insights.sbomify.com/CVE-2026-27976/index.md","name":"CVE-2026-27976","record":{"aliases":["GHSA-59p4-3mhm-qm3r"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Zed code editor","requires_auth":"none","summary":"Attackers can escape the extension sandbox and execute arbitrary code on the host by exploiting symlink handling in the tar extractor.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zed","vendor":"zed"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"}],"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 -\u003e /`), 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Zed Extension Sandbox Escape via Tar Symlink Following","id":"CVE-2026-27976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Next.js: null origin can bypass dev HMR websocket CSRF checks","id":"CVE-2026-27977"},"packages":[],"prev":{"headline":"Ajenti has a potential Remote Code Execution","id":"CVE-2026-27975"},"products":["zed"],"published":"2026-02-25","related":[{"cvss_score":8.6,"headline":"Zed: Remote Command Injection via Unquoted Environment Variable Keys (SSH / WSL Remote)","id":"CVE-2026-44461","kev_date_added":null,"published":"2026-05-28"},{"cvss_score":8.6,"headline":"Zed: Allowlist Bypass via Environment Variable Injection in Terminal Tool Permissions","id":"CVE-2026-44463","kev_date_added":null,"published":"2026-05-28"},{"cvss_score":8.6,"headline":"Zed: Zed IDE Arbitrary Code Execution via untrusted repository with poisoned .git/config","id":"CVE-2026-44465","kev_date_added":null,"published":"2026-05-28"},{"cvss_score":8.6,"headline":"Zed: Allowlist Bypass via Bash Arithmetic Expansion in Terminal Tool Permissions","id":"CVE-2026-44466","kev_date_added":null,"published":"2026-05-28"},{"cvss_score":7.8,"headline":"Zed IDE LSP Binary Configuration Arbitrary Code Execution","id":"CVE-2025-68432","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":7.8,"headline":"Zed IDE MCP Context Server Configuration Arbitrary Code Execution","id":"CVE-2025-68433","kev_date_added":null,"published":"2025-12-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-27","vendors":["zed-industries"]},"summary":"Attackers can escape the extension sandbox and execute arbitrary code on the host by exploiting symlink handling in the tar extractor.","url":"https://insights.sbomify.com/CVE-2026-27976/"}