{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119981 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119981 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119981 is a high-severity vulnerability in Microsoft Visual Studio Code, published on 10 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119981 and fix it if it is affected.\n\nWhat it is: CVE-2026-119981 is a high-severity vulnerability in Microsoft Visual Studio Code, published on 10 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-119981 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-2026-119981/ (Markdown: https://insights.sbomify.com/CVE-2026-119981/index.md)","id":"CVE-2026-119981","markdown":"https://insights.sbomify.com/CVE-2026-119981/index.md","name":"CVE-2026-119981","record":{"aliases":["GHSA-f9x8-48p9-m4wp"],"analysis":null,"analysis_generated_by":null,"assigner":"microsoft","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Missing authentication for critical function in Visual Studio Code allows an authorized attacker to elevate privileges locally.","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 Elevation of Privilege Vulnerability","id":"CVE-2026-119981","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Visual Studio Code Security Feature Bypass Vulnerability","id":"CVE-2026-119982"},"nickname":null,"packages":[],"prev":{"headline":"The UsersWP – Front-end login form, User Registration, User Profile \u0026 Members Directory plugin for WordPress is vulnerable to unauthorized a","id":"CVE-2026-119980"},"products":["Visual Studio Code"],"published":"2026-11-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-11-12","vendors":["Microsoft"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119981/"}