{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2025-49739 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-49739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-49739 is a high-severity path traversal vulnerability in Microsoft Visual Studio, published on 8 Jul 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-49739 and fix it if it is affected.\n\nWhat it is: CVE-2025-49739 is a high-severity path traversal vulnerability in Microsoft Visual Studio, published on 8 Jul 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-49739 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio. 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-49739/ (Markdown: https://insights.sbomify.com/CVE-2025-49739/index.md)","id":"CVE-2025-49739","markdown":"https://insights.sbomify.com/CVE-2025-49739/index.md","name":"CVE-2025-49739","record":{"aliases":["GHSA-cf69-g2cj-5w8c"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Visual Studio IDE","requires_auth":"none","summary":"An attacker can elevate privileges via improper link resolution in Visual Studio, requiring a patch to mitigate the risk.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio","vendor":"microsoft"},{"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-59","name":"Improper Link Resolution Before File Access"}],"description":"Improper link resolution before file access ('link following') in Visual Studio allows an unauthorized attacker to elevate privileges over a network.","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 Elevation of Privilege Vulnerability","id":"CVE-2025-49739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio","products":["microsoft:visual_studio","microsoft:visual_studio_2017","microsoft:visual_studio_2019","microsoft:visual_studio_2022"],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Windows SmartScreen Security Feature Bypass Vulnerability","id":"CVE-2025-49740"},"packages":[],"prev":{"headline":"Microsoft PC Manager Elevation of Privilege Vulnerability","id":"CVE-2025-49738"},"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.14","Microsoft Visual Studio 2022 version 17.8"],"published":"2025-07-08","related":[{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35777","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35825","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35826","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35827","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":7.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2024-20656","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":7.8,"headline":"Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability","id":"CVE-2021-28313","kev_date_added":null,"published":"2021-04-13"}],"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-02-26","vendors":["Microsoft"]},"summary":"An attacker can elevate privileges via improper link resolution in Visual Studio, requiring a patch to mitigate the risk.","url":"https://insights.sbomify.com/CVE-2025-49739/"}