{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-16977 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-16977 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-16977 is a high-severity code injection vulnerability in Microsoft Visual Studio Code, published on 16 Oct 2020. 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-2020-16977 and fix it if it is affected.\n\nWhat it is: CVE-2020-16977 is a high-severity code injection vulnerability in Microsoft Visual Studio Code, published on 16 Oct 2020. 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-2020-16977 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-2020-16977/ (Markdown: https://insights.sbomify.com/CVE-2020-16977/index.md)","id":"CVE-2020-16977","markdown":"https://insights.sbomify.com/CVE-2020-16977/index.md","name":"CVE-2020-16977","record":{"aliases":["GHSA-f757-5gm7-m88x"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VS Code Python extension","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious Jupyter notebooks in VS Code with the Python extension.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_code","vendor":"microsoft"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C","version":"3.1"},"cwes":[],"description":"\u003cp\u003eA remote code execution vulnerability exists in Visual Studio Code when the Python extension loads a Jupyter notebook file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.\u003c/p\u003e\n\u003cp\u003eTo exploit this vulnerability, an attacker would need to convince a target to open a specially crafted file in Visual Studio Code with the Python extension installed.\u003c/p\u003e\n\u003cp\u003eThe update addresses the vulnerability by modifying the way Visual Studio Code Python extension renders notebook content.\u003c/p\u003e","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 Python Extension Remote Code Execution Vulnerability","id":"CVE-2020-16977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_code","products":["microsoft:visual_studio_code"],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Microsoft Dynamics 365 (On-Premise) Cross Site Scripting Vulnerability","id":"CVE-2020-16978"},"packages":[],"prev":{"headline":"Windows Backup Service Elevation of Privilege Vulnerability","id":"CVE-2020-16976"},"products":["Python extension for Visual Studio Code"],"published":"2020-10-16","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Microsoft"]},"summary":"Attackers can execute arbitrary code by tricking users into opening malicious Jupyter notebooks in VS Code with the Python extension.","url":"https://insights.sbomify.com/CVE-2020-16977/"}