GHSA-87vj-4hqv-22p9 CVE-2026-96233
Microsoft Security Advisory CVE-2026-96233 - .NET and Visual Studio Denial of Service Vulnerability
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.99%
- Chance of exploitation in the next 30 days. Higher than 62.55% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-787 Out-of-bounds Write
- Fix
- Available
- 12 packages have a fixed version
Description
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in System.Runtime. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
DateTime Hebrew-number parsing can read outside expected stack bounds and terminate the process.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/481
CVSS Details
-
Version: 3.1
-
Severity: High
-
Score: 7.5
-
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H -
Weakness: CWE-787 (Out-of-bounds Write)
Affected Platforms
- Platforms: Windows, Linux, macOS
- Architectures: All
<a name="affected-packages"></a>Affected Packages
The vulnerability affects Microsoft .NET projects that use an affected package version listed below.
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
If using a package listed in affected packages, you're exposed to the vulnerability.
<a name="how-fix"></a>How do I fix the issue?
- To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
- If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the
dotnet --infocommand.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
Other Information
Reporting Security Issues
If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
Acknowledgements
- s3zer0
Revisions
V1.0 (10/13/2026): Advisory published.
Affected versions
NuGet
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
Microsoft.NETCore.App.Runtime.linux-arm NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-arm --version 10.0.13
Microsoft.NETCore.App.Runtime.linux-arm64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-arm64 --version 10.0.13
Microsoft.NETCore.App.Runtime.linux-musl-arm NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-arm --version 10.0.13
Microsoft.NETCore.App.Runtime.linux-musl-arm64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-arm64 --version 10.0.13
Microsoft.NETCore.App.Runtime.linux-musl-x64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-x64 --version 10.0.13
Microsoft.NETCore.App.Runtime.linux-x64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-x64 --version 10.0.13
Microsoft.NETCore.App.Runtime.osx-arm64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.osx-arm64 --version 10.0.13
Microsoft.NETCore.App.Runtime.osx-x64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.osx-x64 --version 10.0.13
Microsoft.NETCore.App.Runtime.win-arm NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-arm --version 10.0.13
Microsoft.NETCore.App.Runtime.win-arm64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-arm64 --version 10.0.13
Microsoft.NETCore.App.Runtime.win-x64 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-x64 --version 10.0.13
Microsoft.NETCore.App.Runtime.win-x86 NuGet → 10.0.13
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 10.0.13
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-787: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How to prevent it
- Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.
- Operation, Build and Compilation: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Implementation: Consider adhering to the following rules when allocating and managing an application's memory: Double check that the buffer is as large as specified. When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string. Check buffer boundaries if accessing the buffer in a loop and make sure there is no danger of writing past the allocated space. If necessary, truncate all input strings to a reasonable length before passing them to the copy and concatenation functions.
- Operation, Build and Compilation: Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
- Operation: Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336].
- Implementation: Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| CVE-2020-1147 .NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability | High Known exploited | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-2j93-m82w-73j2 Microsoft Security Advisory CVE-2026-96231 - .NET and Visual Studio Elevation of Privilege Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-w6wh-p4g7-mpj2 Microsoft Security Advisory CVE-2026-96225 - .NET and Visual Studio Elevation of Privilege Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-4mpw-cpwj-hxxj Microsoft Security Advisory CVE-2026-70197 - .NET and Visual Studio Remote Code Execution Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-fqpq-cx42-9jmm Microsoft Security Advisory CVE-2026-70194 - .NET and Visual Studio Security Feature Bypass Vulnerability | Medium | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-3rxq-g8rj-r2cf Microsoft Security Advisory CVE-2026-69651 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-wxxw-5cvc-53j7 Microsoft Security Advisory CVE-2026-66822 - .NET and Visual Studio Information Disclosure Vulnerability | Medium | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-mc4q-93x5-f6hj Microsoft Security Advisory CVE-2026-58280 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor