Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-43498: .NET and Visual Studio Remote Code Execution Vulnerability

70
This week
CRITICAL 9.8REMOTEWATCHLISTDOWNGRADEUPGRADE

CVE-2024-43498 is a critical-severity flaw (CVSS 9.8) affecting .net, visual studio 2022. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

.NET and Visual Studio Remote Code Execution Vulnerability

Why this priority

  • Critical severity
  • CISA SSVC: automatable with total technical impact
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.6% (top 11%)
CISA exploited listNo
WeaknessCWE-843
Published2024-11-12
Last modified2026-06-17
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

microsoft .net DOWNGRADE
Affected: 9.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 9.0.0
1. Check installed version
apt-cache policy .net || rpm -q .net || .net --version
2. No fixed release: DOWNGRADE to a release before 9.0.0 (Debian / Ubuntu)
apt-cache madison .net sudo apt install .net=<VERSION_BEFORE_9.0.0> sudo apt-mark hold .net
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list .net sudo dnf downgrade .net-<VERSION_BEFORE_9.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.
microsoft visual studio 2022 UPGRADE
Affected: >= 17.6 and < 17.6.21 · >= 17.8 and < 17.8.16 · >= 17.10.0 and < 17.10.9 · >= 17.11.0 and < 17.11.6
Fixed in: 17.6.21, 17.8.16, 17.10.9, 17.11.6
Safe to downgrade to: a release before 17.6
1. Check installed version
apt-cache policy visual-studio-2022 || rpm -q visual-studio-2022 || visual-studio-2022 --version
2. UPGRADE to 17.6.21 (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.6 (Debian / Ubuntu)
apt-cache madison visual-studio-2022 sudo apt install visual-studio-2022=<VERSION_BEFORE_17.6> 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.6> 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.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
NuGet (.NET) · System.Formats.Nrbf · FIXED · 9.0.0 · vulnerable: < 9.0.0 · source
dotnet add package System.Formats.Nrbf --version 9.0.0
Fedora 46 · byobu · FIXED · 7.23-1.fc46 · FEDORA-2026-08f2b53446 · source
sudo dnf upgrade --advisory=FEDORA-2026-08f2b53446
Ubuntu 22.04 · dotnet6 · NOT AFFECTED
Ubuntu 22.04 · dotnet8 · NOT AFFECTED
Ubuntu 24.04 · dotnet8 · NOT AFFECTED
Ubuntu 24.10 · dotnet8 · NOT AFFECTED
Ubuntu 24.10 · dotnet9 · FIXED · 9.0.100-9.0.0-0ubuntu1~24.10.1
sudo apt update && sudo apt install --only-upgrade dotnet9 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' dotnet9)" ge "9.0.100-9.0.0-0ubuntu1~24.10.1" && echo PATCHED || echo STILL-VULNERABLE
RHEL 9 · dotnet9.0 · FIXED · dotnet9.0-9.0.100-1.el9_5
sudo dnf upgrade --advisory=RHSA-2024:9543 rpm -q dotnet9.0
RHEL 10 · dotnet8.0 · NOT AFFECTED
RHEL 10 · dotnet9.0 · NOT AFFECTED
RHEL 8 · dotnet6.0 · NOT AFFECTED
RHEL 8 · dotnet8.0 · NOT AFFECTED
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-2024-43498?

.net: downgrade or apply the listed mitigation; visual studio 2022: upgrade to 17.6.21, 17.8.16, 17.10.9, 17.11.6. Exact commands for each OS are on this page.

Is CVE-2024-43498 being exploited?

CVE-2024-43498 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-2024-43498 affect?

CVE-2024-43498 affects .net, visual studio 2022. Severity is critical (CVSS 9.8). .NET and Visual Studio Remote Code Execution Vulnerability

How urgent is CVE-2024-43498?

Priority 70/100. Critical severity; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Visual Studio vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.