Microsoft .NET Framework prior 4.8.9332.0 race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.2$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in Microsoft .NET Framework. This affects an unknown function. Such manipulation leads to race condition. This vulnerability is referenced as CVE-2026-32226. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Microsoft .NET Framework and classified as problematic. Affected by this issue is an unknown code block. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. Impacted is availability.

The weakness was published 04/14/2026 as confirmed security update guide (Website). The advisory is available at msrc.microsoft.com. This vulnerability is handled as CVE-2026-32226. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/18/2026).

Upgrading to version 2.0.50727.9068, 3.0.30729.9065, 4.7.4141.0, 2.0.50727.9068, 3.0.30729.9065, 4.8.4801.0, 2.0.50727.9181, 3.0.30729.9165, 4.8.4801.0, 2.0.50727.9181, 3.0.30729.9165, 4.8.9332.0 or 4.8.4801.0 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1100). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Microsoft .NET Framework
  • Microsoft PowerShell
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • Oracle Linux
  • Microsoft .NET
  • Microsoft Visual Studio 2017
  • Microsoft Visual Studio Code
  • Microsoft Visual Studio 2022
  • Microsoft Visual Studio 2019

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.2

VulDB Base Score: 5.9
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 5.9
Vendor Vector (Microsoft): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Unproven

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒

Upgrade: .NET Framework 2.0.50727.9068/3.0.30729.9065/4.7.4141.0/2.0.50727.9068/3.0.30729.9065/4.8.4801.0/2.0.50727.9181/3.0.30729.9165/4.8.4801.0/2.0.50727.9181/3.0.30729.9165/4.8.9332.0/4.8.4801.0

Timelineinfo

04/14/2026 VulDB entry created
04/14/2026 +0 days Advisory disclosed
04/14/2026 +0 days Countermeasure disclosed
04/18/2026 +4 days VulDB entry last update

Sourcesinfo

Vendor: microsoft.com

Advisory: msrc.microsoft.com
Status: Confirmed

CVE: CVE-2026-32226 (🔒)
GCVE (CVE): GCVE-0-2026-32226
GCVE (VulDB): GCVE-100-357530
CERT Bund: WID-SEC-2026-1100 - Microsoft DeveloperTools: Mehrere Schwachstellen

Entryinfo

Created: 04/14/2026 20:47
Updated: 04/18/2026 19:51
Changes: 04/14/2026 20:47 (36), 04/14/2026 20:50 (33), 04/18/2026 19:51 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!