{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46508 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46508 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46508 is a high-severity command injection vulnerability in vercel turborepo, published on 15 May 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-46508 and fix it if it is affected.\n\nWhat it is: CVE-2026-46508 is a high-severity command injection vulnerability in vercel turborepo, published on 15 May 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: There is no known exploitation of CVE-2026-46508 in the wild and no public exploit code.\n\nAffected product: vercel turborepo. 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-46508/ (Markdown: https://insights.sbomify.com/CVE-2026-46508/index.md)","id":"CVE-2026-46508","markdown":"https://insights.sbomify.com/CVE-2026-46508/index.md","name":"CVE-2026-46508","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VSCode extension","requires_auth":"none","summary":"A malicious workspace can execute arbitrary shell commands via the Turborepo VSCode extension, compromising the local developer environment.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"turborepo_language_server_protocol","vendor":"vercel"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"Turborepo is a high-performance build system for JavaScript and TypeScript codebases. Prior to 2.9.14000, the Turborepo LSP VS Code extension could execute shell commands derived from workspace-controlled values. The extension used string-based command execution for Turborepo daemon commands and task runs. A malicious workspace could provide crafted values through workspace settings or task names in the repository's source code that were interpolated into shell commands. When the extension activated or when a user ran a task through the extension, those values could be interpreted by the user's shell, allowing arbitrary command execution with the privileges of the local VS Code process. This vulnerability is fixed in 2.9.14000.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Turborepo: VSCode Extension command injection","id":"CVE-2026-46508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"deepobj: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')","id":"CVE-2026-46509"},"packages":[],"prev":{"headline":"OpenAM Arbitrary OAuth Token Minting via Push Registration","id":"CVE-2026-46498"},"products":["turborepo"],"published":"2026-05-15","related":[],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-15","vendors":["vercel"]},"summary":"A malicious workspace can execute arbitrary shell commands via the Turborepo VSCode extension, compromising the local developer environment.","url":"https://insights.sbomify.com/CVE-2026-46508/"}