{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27967 exists.","fix":"No fix has been published for CVE-2026-27967 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27967 is a high-severity path traversal vulnerability in zed-industries zed, published on 25 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-27967 and fix it if it is affected.\n\nWhat it is: CVE-2026-27967 is a high-severity path traversal vulnerability in zed-industries zed, published on 25 Feb 2026. It can only be exploited from the same machine or local network, 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-27967 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-27967/ (Markdown: https://insights.sbomify.com/CVE-2026-27967/index.md)","id":"CVE-2026-27967","markdown":"https://insights.sbomify.com/CVE-2026-27967/index.md","name":"CVE-2026-27967","record":{"aliases":["GHSA-786m-x2vc-5235"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Zed code editor","requires_auth":"none","summary":"Attackers can read or write files outside the project directory via symlinks, bypassing privacy protections and potentially leaking sensitive data to the LLM.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zed","vendor":"zed"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Zed, a code editor, has a symlink escape vulnerability in versions prior to 0.225.9 in Agent file tools (`read_file`, `edit_file`). It allows reading and writing files **outside the project directory** when a project contains symbolic links pointing to external paths. This bypasses the intended workspace boundary and privacy protections (`file_scan_exclusions`, `private_files`), potentially leaking sensitive user data to the LLM. Version 0.225.9 fixes 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":"Symlink Escape in Agent File Tools","id":"CVE-2026-27967","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":"Packistry accepts expired access tokens","id":"CVE-2026-27968"},"packages":[],"prev":{"headline":"Langflow has Remote Code Execution in CSV Agent","id":"CVE-2026-27966"},"products":["zed"],"published":"2026-02-25","related":[{"cvss_score":8.8,"headline":"Zed Extension Sandbox Escape via Tar Symlink Following","id":"CVE-2026-27976","kev_date_added":null,"published":"2026-02-25"},{"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-28","vendors":["zed-industries"]},"summary":"Attackers can read or write files outside the project directory via symlinks, bypassing privacy protections and potentially leaking sensitive data to the LLM.","url":"https://insights.sbomify.com/CVE-2026-27967/"}