PatchTheCVECVE-2026-47305: Protection mechanism failure in Visual Studio allows an unauthorized attacker to execute code locally.
42
This month
HIGH 7.8WATCHLISTUPGRADEUPGRADE
CVE-2026-47305 is a high-severity flaw (CVSS 7.8) affecting visual studio 2022, visual studio 2026. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Protection mechanism failure in Visual Studio allows an unauthorized attacker to execute code locally.
Why this priority
- High severity
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 60%) |
| CISA exploited list | No |
| Weakness | CWE-693 |
| Published | 2026-07-14 |
| Last modified | 2026-07-16 |
Publisher (CNA): Microsoft Corporation · Vendor: microsoft
Last updated 2026-07-16 · 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 2022 UPGRADE
Affected: >= 17.12.0 and < 17.12.22 · >= 17.14.0 and < 17.14.36
Fixed in: 17.12.22, 17.14.36
Safe to downgrade to: a release before 17.12.0
1. Check installed version
apt-cache policy visual-studio-2022 || rpm -q visual-studio-2022 || visual-studio-2022 --version
2. UPGRADE to 17.12.22 (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.12.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2022
sudo apt install visual-studio-2022=<VERSION_BEFORE_17.12.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.12.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.
microsoft visual studio 2026 UPGRADE
Affected: >= 18.7.0 and < 18.7.4
Fixed in: 18.7.4
Safe to downgrade to: a release before 18.7.0
1. Check installed version
apt-cache policy visual-studio-2026 || rpm -q visual-studio-2026 || visual-studio-2026 --version
2. UPGRADE to 18.7.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-2026
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-2026
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 18.7.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2026
sudo apt install visual-studio-2026=<VERSION_BEFORE_18.7.0>
sudo apt-mark hold visual-studio-2026
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-2026
sudo dnf downgrade visual-studio-2026-<VERSION_BEFORE_18.7.0>
sudo dnf versionlock add visual-studio-2026
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-2026-47305?
visual studio 2022: upgrade to 17.12.22, 17.14.36; visual studio 2026: upgrade to 18.7.4. Exact commands for each OS are on this page.
Is CVE-2026-47305 being exploited?
CVE-2026-47305 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-2026-47305 affect?
CVE-2026-47305 affects visual studio 2022, visual studio 2026. Severity is high (CVSS 7.8). Protection mechanism failure in Visual Studio allows an unauthorized attacker to execute code locally.
How urgent is CVE-2026-47305?
Priority 42/100. High severity; On your watchlist
Software pages
Related CVEs
- CVE-2026-32178 HIGH 7.5 UPGRADE UPGRADE Improper neutralization of special elements in .NET allows an unauthorized attacker to perform spoofing over a
- CVE-2026-32203 HIGH 7.5 UPGRADE UPGRADE Stack-based buffer overflow in .NET and Visual Studio allows an unauthorized attacker to deny service over a n
- CVE-2022-24513 HIGH 7.8 UPGRADE UPGRADE Visual Studio Elevation of Privilege Vulnerability
- CVE-2026-96957 HIGH 8.8 UPGRADE UPGRADE Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security
- CVE-2026-62886 HIGH 7.8 UPGRADE UPGRADE Integer overflow or wraparound in .NET allows an unauthorized attacker to elevate privileges locally.