{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-21178 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-21178 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-21178 is a high-severity memory corruption vulnerability in Microsoft Visual Studio 2017, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-21178 and fix it if it is affected.\n\nWhat it is: CVE-2025-21178 is a high-severity memory corruption vulnerability in Microsoft Visual Studio 2017, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-21178 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio 2017. 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-2025-21178/ (Markdown: https://insights.sbomify.com/CVE-2025-21178/index.md)","id":"CVE-2025-21178","markdown":"https://insights.sbomify.com/CVE-2025-21178/index.md","name":"CVE-2025-21178","record":{"aliases":["GHSA-7qvp-9xw6-rpfp"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Visual Studio IDE","requires_auth":"none","summary":"An attacker can execute arbitrary code by exploiting memory corruption vulnerabilities in Microsoft Visual Studio.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_2017","vendor":"microsoft"},{"product":"visual_studio_2019","vendor":"microsoft"},{"product":"visual_studio_2022","vendor":"microsoft"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"Visual Studio 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 Remote Code Execution Vulnerability","id":"CVE-2025-21178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_2017","products":["microsoft:visual_studio_2017","microsoft:visual_studio_2019","microsoft:visual_studio_2022"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"DHCP Client Service Denial of Service Vulnerability","id":"CVE-2025-21179"},"packages":[],"prev":{"headline":"Microsoft Dynamics 365 Sales Elevation of Privilege Vulnerability","id":"CVE-2025-21177"},"products":["Microsoft Visual Studio 2015 Update 3","Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)","Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)","Microsoft Visual Studio 2022 version 17.10","Microsoft Visual Studio 2022 version 17.12","Microsoft Visual Studio 2022 version 17.6","Microsoft Visual Studio 2022 version 17.8"],"published":"2025-01-14","related":[{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1349","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1350","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1352","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1354","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":7.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2023-28296","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2023-21566","kev_date_added":null,"published":"2023-02-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":"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-06-09","vendors":["Microsoft"]},"summary":"An attacker can execute arbitrary code by exploiting memory corruption vulnerabilities in Microsoft Visual Studio.","url":"https://insights.sbomify.com/CVE-2025-21178/"}