{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25805 exists.","fix":"No fix has been published for CVE-2026-25805 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25805 is a medium-severity vulnerability in zed-industries zed, published on 10 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-25805 and fix it if it is affected.\n\nWhat it is: CVE-2026-25805 is a medium-severity vulnerability in zed-industries zed, published on 10 Feb 2026. An attacker needs administrator access to exploit it, 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-25805 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-25805/ (Markdown: https://insights.sbomify.com/CVE-2026-25805/index.md)","id":"CVE-2026-25805","markdown":"https://insights.sbomify.com/CVE-2026-25805/index.md","name":"CVE-2026-25805","record":{"aliases":["GHSA-f2g4-87h6-4pxq"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Zed code editor","requires_auth":"high_privilege","summary":"Zed editor fails to display MCP tool call parameters, preventing users from detecting malicious tool poisoning during execution.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zed","vendor":"zed"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-356","name":"Missing User Interaction for Potentially Unsafe Action"}],"description":"Zed is a multiplayer code editor. Prior to 0.219.4, Zed does not show with which parameters a tool is being invoked, when asking for allowance. Further it does not show after the tool was being invoked, which parameters were used. Thus, maybe unwanted or even malicious values could be used without the user having a chance to notice it. Patched in Zed Editor 0.219.4 which includes expandable tool call details.","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 does not show Parameter Values for MCP Tool Calls. Users cannot detect tool poisoning.","id":"CVE-2026-25805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PlaciPy has Missing Authorization Checks on Student Management Endpoints (IDOR)","id":"CVE-2026-25806"},"packages":[],"prev":{"headline":"Antrea has invalid enforcement order for network policy rules caused by integer overflow","id":"CVE-2026-25804"},"products":["zed"],"published":"2026-02-10","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-10","vendors":["zed-industries"]},"summary":"Zed editor fails to display MCP tool call parameters, preventing users from detecting malicious tool poisoning during execution.","url":"https://insights.sbomify.com/CVE-2026-25805/"}