PatchTheCVECVE-2025-49739: Improper link resolution before file access ('link following') in Visual Studio allows an unauthorized attacke
51
This month
HIGH 8.8WATCHLISTDOWNGRADEUPGRADEUPGRADE
CVE-2025-49739 is a high-severity flaw (CVSS 8.8) affecting visual studio, visual studio 2017, visual studio 2019. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Improper link resolution before file access ('link following') in Visual Studio allows an unauthorized attacker to elevate privileges over a network.
Why this priority
- High severity
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.9% (top 39%) |
| CISA exploited list | No |
| Weakness | CWE-59 |
| Published | 2025-07-08 |
| Last modified | 2026-06-17 |
Publisher (CNA): Microsoft Corporation · Vendor: microsoft
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
microsoft visual studio DOWNGRADE
Affected: 2015 update3
Fixed in: no fixed release known
Safe to downgrade to: a release before 2015
1. Check installed version
apt-cache policy visual-studio || rpm -q visual-studio || visual-studio --version
2. No fixed release: DOWNGRADE to a release before 2015 (Debian / Ubuntu)
apt-cache madison visual-studio
sudo apt install visual-studio=<VERSION_BEFORE_2015>
sudo apt-mark hold visual-studio
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio
sudo dnf downgrade visual-studio-<VERSION_BEFORE_2015>
sudo dnf versionlock add visual-studio
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
microsoft visual studio 2017 UPGRADE
Affected: >= 15.0 and < 15.9.75
Fixed in: 15.9.75
Safe to downgrade to: a release before 15.0
1. Check installed version
apt-cache policy visual-studio-2017 || rpm -q visual-studio-2017 || visual-studio-2017 --version
2. UPGRADE to 15.9.75 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-2017
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-2017
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 15.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2017
sudo apt install visual-studio-2017=<VERSION_BEFORE_15.0>
sudo apt-mark hold visual-studio-2017
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-2017
sudo dnf downgrade visual-studio-2017-<VERSION_BEFORE_15.0>
sudo dnf versionlock add visual-studio-2017
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
microsoft visual studio 2019 UPGRADE
Affected: >= 16.0 and < 16.11.49
Fixed in: 16.11.49
Safe to downgrade to: a release before 16.0
1. Check installed version
apt-cache policy visual-studio-2019 || rpm -q visual-studio-2019 || visual-studio-2019 --version
2. UPGRADE to 16.11.49 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-2019
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-2019
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 16.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2019
sudo apt install visual-studio-2019=<VERSION_BEFORE_16.0>
sudo apt-mark hold visual-studio-2019
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-2019
sudo dnf downgrade visual-studio-2019-<VERSION_BEFORE_16.0>
sudo dnf versionlock add visual-studio-2019
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
microsoft visual studio 2022 UPGRADE
Affected: >= 17.8.0 and < 17.8.23 · >= 17.10.0 and < 17.10.17 · >= 17.12.0 and < 17.12.10 · >= 17.14.0 and < 17.14.8
Fixed in: 17.8.23, 17.10.17, 17.12.10, 17.14.8
Safe to downgrade to: a release before 17.8.0
1. Check installed version
apt-cache policy visual-studio-2022 || rpm -q visual-studio-2022 || visual-studio-2022 --version
2. UPGRADE to 17.8.23 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-2022
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-2022
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 17.8.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2022
sudo apt install visual-studio-2022=<VERSION_BEFORE_17.8.0>
sudo apt-mark hold visual-studio-2022
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-2022
sudo dnf downgrade visual-studio-2022-<VERSION_BEFORE_17.8.0>
sudo dnf versionlock add visual-studio-2022
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-49739?
visual studio: downgrade or apply the listed mitigation; visual studio 2017: upgrade to 15.9.75; visual studio 2019: upgrade to 16.11.49. Exact commands for each OS are on this page.
Is CVE-2025-49739 being exploited?
CVE-2025-49739 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-49739 affect?
CVE-2025-49739 affects visual studio, visual studio 2017, visual studio 2019. Severity is high (CVSS 8.8). Improper link resolution before file access ('link following') in Visual Studio allows an unauthorized attacker to elevate privileges over a network.
How urgent is CVE-2025-49739?
Priority 51/100. High severity; On your watchlist
Software pages
Related CVEs
- CVE-2024-43603 MEDIUM 5.5 DOWNGRADE UPGRADE Visual Studio Collector Service Denial of Service Vulnerability