CVE-2026-32177: Heap-based buffer overflow in .NET allows an unauthorized attacker to elevate privileges locally.

This month

HIGH 7.3WATCHLISTUPGRADEUPGRADEDOWNGRADE

CVE-2026-32177 is a high-severity flaw (CVSS 7.3) affecting visual studio 2022, visual studio 2026, .net framework. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Heap-based buffer overflow in .NET allows an unauthorized attacker to elevate privileges locally.

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-20, CWE-122, CWE-787
Published	2026-05-12
Last modified	2026-07-15

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-07-15 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-12 18:16 UTCPublished CVE record published
2026-07-15 02:19 UTCUpdated Record last modified

microsoft visual studio 2022 UPGRADE

Affected: >= 17.12.0 and < 17.12.20 · >= 17.14.0 and < 17.14.32

Fixed in: 17.12.20, 17.14.32

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.20 (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.5.0 and < 18.5.3

Fixed in: 18.5.3

Safe to downgrade to: a release before 18.5.0

1. Check installed version

apt-cache policy visual-studio-2026 || rpm -q visual-studio-2026 || visual-studio-2026 --version

2. UPGRADE to 18.5.3 (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.5.0 (Debian / Ubuntu)

apt-cache madison visual-studio-2026 sudo apt install visual-studio-2026=<VERSION_BEFORE_18.5.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.5.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.

microsoft .net framework DOWNGRADE

Affected: 4.8 · 4.6.2 · 4.7 · 4.7.1 · 4.7.2 · 3.5 · 4.8.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.5

1. Check installed version

apt-cache policy .net-framework || rpm -q .net-framework || .net-framework --version

2. No fixed release: DOWNGRADE to a release before 3.5 (Debian / Ubuntu)

apt-cache madison .net-framework sudo apt install .net-framework=<VERSION_BEFORE_3.5> sudo apt-mark hold .net-framework

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list .net-framework sudo dnf downgrade .net-framework-<VERSION_BEFORE_3.5> sudo dnf versionlock add .net-framework

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 .net UPGRADE

Affected: >= 8.0.0 and < 8.0.27 · >= 9.0.0 and < 9.0.16 · >= 10.0.0 and < 10.0.8

Fixed in: 8.0.27, 9.0.16, 10.0.8

Safe to downgrade to: a release before 8.0.0

1. Check installed version

apt-cache policy .net || rpm -q .net || .net --version

2. UPGRADE to 8.0.27 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade .net

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade .net

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 8.0.0 (Debian / Ubuntu)

apt-cache madison .net sudo apt install .net=<VERSION_BEFORE_8.0.0> sudo apt-mark hold .net

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list .net sudo dnf downgrade .net-<VERSION_BEFORE_8.0.0> sudo dnf versionlock add .net

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.

Quick answers

How do I fix CVE-2026-32177?

visual studio 2022: upgrade to 17.12.20, 17.14.32; visual studio 2026: upgrade to 18.5.3; .net framework: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-32177 being exploited?

CVE-2026-32177 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-32177 affect?

CVE-2026-32177 affects visual studio 2022, visual studio 2026, .net framework. Severity is high (CVSS 7.3). Heap-based buffer overflow in .NET allows an unauthorized attacker to elevate privileges locally.

How urgent is CVE-2026-32177?

Priority 43/100. High severity; On your watchlist

Software pages

.NET vulnerabilities · Visual Studio vulnerabilities

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.

References

← Back to latest CVEs