{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21991 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-21991 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21991 is a high-severity code injection vulnerability in Microsoft Visual Studio Code, published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21991 and fix it if it is affected.\n\nWhat it is: CVE-2022-21991 is a high-severity code injection vulnerability in Microsoft Visual Studio Code, published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-21991 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio Code. 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-2022-21991/ (Markdown: https://insights.sbomify.com/CVE-2022-21991/index.md)","id":"CVE-2022-21991","markdown":"https://insights.sbomify.com/CVE-2022-21991/index.md","name":"CVE-2022-21991","record":{"aliases":["GHSA-2gx5-p7gf-5xrc"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VS Code extension","requires_auth":"none","summary":"Attackers can execute arbitrary code via the Visual Studio Code Remote Development Extension, requiring developers to update the tool.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_code","vendor":"microsoft"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C","version":"3.1"},"cwes":[],"description":"Visual Studio Code Remote Development Extension Remote Code Execution Vulnerability","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":"Visual Studio Code Remote Development Extension Remote Code Execution Vulnerability","id":"CVE-2022-21991","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_code","products":["microsoft:visual_studio_code"],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Windows Mobile Device Management Remote Code Execution Vulnerability","id":"CVE-2022-21992"},"packages":[],"prev":{"headline":"Remote Desktop Client Remote Code Execution Vulnerability","id":"CVE-2022-21990"},"products":["Visual Studio Code"],"published":"2022-02-09","related":[{"cvss_score":9.6,"headline":"Visual Studio Code Security Feature Bypass Vulnerability","id":"CVE-2026-81376","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":9.6,"headline":"Visual Studio Code Elevation of Privilege Vulnerability","id":"CVE-2026-47281","kev_date_added":null,"published":"2026-06-09"},{"cvss_score":8.8,"headline":"Visual Studio Code Security Feature Bypass Vulnerability","id":"CVE-2026-78462","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":8.8,"headline":"Visual Studio Code Remote Code Execution Vulnerability","id":"CVE-2026-59113","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":8.8,"headline":"Visual Studio Code Remote Code Execution Vulnerability","id":"CVE-2026-69320","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":8.8,"headline":"Visual Studio Code Remote Code Execution Vulnerability","id":"CVE-2026-70336","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":8.8,"headline":"Visual Studio Code Security Feature Bypass Vulnerability","id":"CVE-2026-57102","kev_date_added":null,"published":"2026-07-14"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["Microsoft"]},"summary":"Attackers can execute arbitrary code via the Visual Studio Code Remote Development Extension, requiring developers to update the tool.","url":"https://insights.sbomify.com/CVE-2022-21991/"}