Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-47304: Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security

44
This month
HIGH 8.1REMOTEWATCHLISTDOWNGRADEUPGRADEUPGRADE

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

Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 79%)
CISA exploited listNo
WeaknessCWE-345, CWE-347
Published2026-07-14
Last modified2026-07-24
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

microsoft .net framework DOWNGRADE
Affected: 4.8.1 · 4.8 · 4.6.2 · 4.7 · 4.7.1 · 4.7.2 · 3.5
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.29 · >= 9.0.0 and < 9.0.18 · >= 10.0.0 and < 10.0.6
Fixed in: 8.0.29, 9.0.18, 10.0.6
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.29 (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.
microsoft visual studio 2017 UPGRADE
Affected: >= 15.0 and <= 15.9
Fixed in: newer than 15.9
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 newer than 15.9 (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
Fixed in: newer than 16.11
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 newer than 16.11 (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.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 · 18.5.0
Fixed in: 18.7.4
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.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.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.

Advisories and coverage

Official advisories

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-47304?

.net framework: downgrade or apply the listed mitigation; .net: upgrade to 8.0.29, 9.0.18, 10.0.6; visual studio 2017: upgrade to newer than 15.9. Exact commands for each OS are on this page.

Is CVE-2026-47304 being exploited?

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

CVE-2026-47304 affects .net framework, .net, visual studio 2017. Severity is high (CVSS 8.1). Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network.

How urgent is CVE-2026-47304?

Priority 44/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

.NET vulnerabilities · 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.