Visit NES for .NET Home Page
.NET 6.0.x Release Notes
Comprehensive release notes and changelog for .NET 6.0.x, including security patches, bug fixes, and feature updates across all supported versions.
103 Patched Vulnerabilities
VEX Statements
.NET 6.0.47 - October 13, 2026
- Version:
6.0.47 - Security fixes in the .NET runtime shared framework — apply to all applications running on the runtime (
Microsoft.NETCore.App):- CVE-2026-96233 A denial-of-service in
DateTimeparsing where Hebrew numerals were stored in a fixed three-slot stack buffer without a bounds check, so a short crafted date string could write past the buffer and terminate the process; the parser now fails such input instead. Applications running in globalization-invariant mode were not exposed. - CVE-2026-96225 An elevation-of-privilege issue on Linux and macOS where named-mutex shared memory lived in a world-writable directory under
/tmp/.dotnet, so another local user could plant a symbolic link and make the runtime change the permissions of an arbitrary directory; named mutexes are now scoped per user by default and the runtime refuses symbolic links in that path. - CVE-2026-96231 An elevation-of-privilege issue in the same named-mutex shared memory, where a planted symbolic link could make the runtime truncate an arbitrary file; covered by the same per-user scope and symbolic-link checks.
- CVE-2026-96233 A denial-of-service in
- Security fixes in
System.Security.Cryptography.XmlandSystem.Security.Cryptography.Pkcs— these ship inside the ASP.NET Core and Windows Desktop shared frameworks (Microsoft.AspNetCore.App,Microsoft.WindowsDesktop.App) and as standalone NuGet packages, nowSystem.Security.Cryptography.Xml6.0.2.3andSystem.Security.Cryptography.Pkcs6.0.5.1. ASP.NET Core and Windows Desktop apps get these fixes from the NES runtime. Other apps that reference either package directly need the NES package, see NuGet packages with NES fixes:- CVE-2026-58280 A denial-of-service in Signed XML processing where deeply nested decrypted XML was re-parsed without a depth limit, exhausting the stack; decrypted fragments are now parsed with a nesting limit.
- CVE-2026-69651 A denial-of-service in
EncryptedXmlwhere a document with manyEncryptedKeyelements in aKeyInfodrove a quadratic number of key decryptions; the number of key decryptions per lookup is now capped. - CVE-2026-96958 An unauthenticated denial-of-service in XML canonicalization where an element carrying a very large number of namespace declarations made C14N processing quadratic; the number of namespace declarations and attributes a transform will process is now capped.
- CVE-2026-96959 An unauthenticated denial-of-service where decryptions nested inside a
CipherReferencetransform were not counted against the outer decryption budget, allowing unbounded recursive work; nested decryptions now count against the same limit. - CVE-2026-96960 An algorithmic denial-of-service in
XmlDecryptionTransformwhere every decryption re-queued the candidates of all siblingEncryptedDataelements, so work grew quadratically; the queued candidates are now capped at 256. - CVE-2026-96222 A spoofing issue in
KeyInfoX509DatawhereLoadXmlaccepted serialized certificate containers (such as PFX data) in anX509Certificateelement instead of a single plain certificate, which could let a forged token pass signature checks in AD FS / WS-Trust style flows; only plain X.509 certificates are now accepted. - CVE-2026-84008 A denial-of-service in
SignedCms.CheckSignaturewhere every signer re-parsed every certificate in the message, so checking a message with many signers took quadratic time; decoded certificates are now cached once per message. - CVE-2026-70162 A denial-of-service on Windows in
EnvelopedCms.Decodewhere unprotected attributes were merged one at a time by OID, making decoding quadratic in the number of attributes; attributes are now added without merging, as on other platforms.
- Security fixes in the ASP.NET Core shared framework — apply to applications running on
Microsoft.AspNetCore.App:- CVE-2026-88092 An HTTP/1.1 request-smuggling issue in Kestrel where, after a connection abort during a request body, the connection loop could continue and parse the unread body bytes as a new request; the HTTP/1.1 loop now stops when the connection is aborted.
- CVE-2026-70188 A header-injection issue in Kestrel's HTTP/2 and HTTP/3 support where carriage-return and line-feed characters in request trailers were passed to the application; trailers containing CR or LF are now rejected.
- CVE-2026-70186 A denial-of-service in Kestrel's HTTP/3 support where a flood of
RESET_STREAMframes could deadlock stream completion; stream aborts no longer run under the completion lock. This only applies to applications that have enabled HTTP/3, which is a preview feature in .NET 6. - CVE-2026-70181 A memory-exhaustion denial-of-service where
FileBufferingReadStreamrented its full in-memory buffer as soon as it was created, so many small concurrent multipart sections over HTTP/2 could pin large amounts of memory; buffers are now rented only as data arrives. - CVE-2026-70196 A CPU-exhaustion denial-of-service in
FormPipeReaderwhere a form body sent in tiny chunks was rescanned from the start on every read; the reader now resumes where it stopped. - CVE-2025-26682 Completes the fix shipped in 6.0.45 for this resource-exhaustion issue in Kestrel's HTTP/3 control stream. The 6.0.45 frame-size limit was checked once per read, so an oversized frame queued behind a small one in the same read was still buffered; the limit is now checked on every frame. This only applies to applications that have enabled HTTP/3, which is a preview feature in .NET 6.
- CVE-2026-70183 An authorization-bypass in Blazor's
AuthorizeViewwhere the result of an earlier, slower authorization check could arrive after a newer one and overwrite it, rendering content for a user who was no longer authorized; superseded results are now discarded.
- Security fixes in opt-in ASP.NET Core packages — apply only to applications that reference them:
- CVE-2026-70179 An elevation-of-privilege in
Microsoft.AspNetCore.Authentication.Negotiatewhere LDAP role lookup matched the Kerberos principal by account name only, so a different directory object with a colliding canonical name could supply its roles; when the authenticated identity carries a primary SID (Windows hosts), the LDAP entry's SID must now match it. On Linux and macOS, where Kerberos identities carry no SID, setting theMicrosoft.AspNetCore.Authentication.Negotiate.RequirePrimarySidClaimswitch skips LDAP role lookup for such identities instead. - CVE-2026-70175 An account-takeover issue in
Microsoft.AspNetCore.Identity.UIwhere the password-reset and email-confirmation pages sent mail to the address typed into the form rather than the address stored on the account, which an accent-insensitive database collation could resolve to a different user; mail now goes to the stored address. Applications using the default Identity UI must update theMicrosoft.AspNetCore.Identity.UIpackage; scaffolded copies of those pages need the same change. - CVE-2026-96230 A cross-site scripting issue in the Blazor WebAssembly debugging page served during development, where an exception message and the
urlquery value were written into the page without HTML encoding; the page now encodes both. - CVE-2026-92707 A memory-exhaustion denial-of-service in MessagePack deserialization where deeply nested arrays reserved memory for elements before reading them; the SignalR MessagePack protocol (
Microsoft.AspNetCore.SignalR.Protocols.MessagePack) now uses MessagePack2.5.307. Blazor Server's built-in MessagePack reader, which ships in the ASP.NET Core shared framework, carries the same fix. - GHSA-7rj2-5w9w-r9jx A process-crash denial-of-service in MessagePack LZ4 decompression where accumulated block lengths could overflow; fixed by moving to MessagePack
2.5.307. SignalR does not enable LZ4 compression. - GHSA-fx6j-x9m5-vmrf A regular-expression denial-of-service in MessagePack's
AssemblyNameVersionSelectorRegex; fixed by moving to MessagePack2.5.307. SignalR does not use the affected assembly-version mismatch option.
- CVE-2026-70179 An elevation-of-privilege in
- Security fix in the opt-in
System.Formats.Cborpackage, now6.0.0.1— applies only to applications that reference it:- A denial-of-service in
CborReaderwhere deeply nested CBOR map keys made duplicate-key checking expensive enough to stall the process; the reader now enforces a maximum nesting depth of 64.
- A denial-of-service in
- Security fixes in Windows Presentation Foundation (WPF) — apply to WPF desktop applications on Windows (
Microsoft.WindowsDesktop.App):- CVE-2026-70007 A heap out-of-bounds write in the pixel-shader bytecode translator, where a
DEFinstruction with a non-constant destination register was counted differently by the translator's two passes, so it wrote more instructions than it had allocated; such shaders are now rejected. - CVE-2026-96224 A heap out-of-bounds write in the pixel-shader bytecode translator caused by
DCLdeclaration tokens that were not validated; such shaders are now rejected. - CVE-2026-96235 A heap out-of-bounds write in the pixel-shader bytecode translator caused by crafted shader bytecode; covered by the same translator bounds checks, which also validate instruction sizes and parameter reads.
- CVE-2026-85363 An out-of-bounds write in hardware-accelerated text rendering where extreme glyph coordinates in an XPS document overflowed 32-bit pointer arithmetic in the glyph bank; the destination address is now computed in 64-bit arithmetic.
- CVE-2026-70035 A remote-code-execution issue where a
Hyperlinkinside XAML loaded through the restrictive XAML reader could navigate without being treated as untrusted; such navigation is now marked unsafe and blocked. - CVE-2026-70174 A remote-code-execution issue where a
Hyperlinkinside aFixedPageof an XPS document bypassed the navigation restrictions applied to restricted content; it is now marked unsafe as well. - CVE-2026-83520 A remote-code-execution issue where restricted XPS and XAML content could create navigation hosts such as
Frame; the restrictive reader now blocks navigation host types. - CVE-2026-87697 A remote-code-execution issue where a navigation re-raised from the root
FixedPageof an XPS document was treated as safe; it is now treated as unsafe. - CVE-2026-96229 A credential-disclosure issue where restricted XPS content could make WPF fetch an absolute remote or UNC address automatically, sending NetNTLMv2 credentials; the restrictive reader now drops such addresses on properties that load content automatically.
- CVE-2026-96232 An information-disclosure issue in the TrueType font subsetter where a crafted font in an XPS document could cause out-of-bounds reads that leaked memory addresses; the subsetter now bounds-checks those reads.
- CVE-2026-96234 A credential-disclosure issue where the zone check that decides whether default credentials may be sent cached a positive DNS result, so DNS poisoning or a stale cache entry could leak Windows credentials to a remote host; positive decisions are no longer cached.
- CVE-2026-70007 A heap out-of-bounds write in the pixel-shader bytecode translator, where a
- Security fixes in the .NET SDK — apply to the
dotnetCLI (all SDK users); the runtime that applications execute on is unaffected. The SDK now bundles the template engineMicrosoft.TemplateEngine.*6.0.427.1:- CVE-2026-96237 A remote-code-execution issue where workload package downloads and integrity repair ignored NuGet Package Source Mapping, so a package could be fetched from an unmapped feed; workload downloads now honor the mapping.
- CVE-2026-70161 An elevation-of-privilege issue where workload manifests could use workload and pack IDs containing path components, letting a malicious manifest import MSBuild targets from outside the workload folder; such IDs are now rejected.
- CVE-2026-70190 An elevation-of-privilege issue on Windows where the elevated workload installer server trusted
%ProgramData%\dotnetwithout checking who owned it, so a junction planted there could redirect privileged file operations; the directory's owner and access rules are now verified before use. - CVE-2026-96238 A security-feature-bypass where
dotnet new --installignored NuGet Package Source Mapping when acquiring templates; template installation now honors the mapping and refuses extra feeds passed on the command line when mapping is enabled.
- Behavior changes in this release:
- Named mutexes on Linux and macOS are now per user. A named mutex created by one user is no longer visible to processes running as a different user. Applications that share a named mutex across user accounts can restore the previous machine-wide behavior by setting the
System.Threading.Mutex.UnsafeDefaultMutexScopeGlobalruntime configuration switch totruein every participating process. KeyInfoX509Dataaccepts only plain X.509 certificates inLoadXml. Set theSystem.Security.Cryptography.Xml.AllowNonCertificateX509Dataswitch to restore the previous behavior.SignedXmldecryption is bounded. A decryption transform that covers more than about 23 siblingEncryptedDataelements now throws at default limits.- WPF restricts more content loaded through the restrictive XAML reader and XPS documents. Each protection has an opt-out switch for compatibility; turn one off only as a short-term measure while you fix the affected content:
Switch.System.Windows.Navigation.OptOutOfRestrictiveXamlNavigationBlock,Switch.System.Windows.Markup.OptOutOfNavigationTypeRestrictiveXamlBlock,Switch.System.Windows.Markup.OptOutOfRestrictiveXamlUriBlock,Switch.MS.Internal.TtfDelta.DisableFontSecurityProtectionandSwitch.MS.Internal.WpfGfx.DisableWpfGfxBoundsCheckProtection. dotnet new --installrefuses--nuget-source/--add-sourcewhen NuGet Package Source Mapping is enabled. Add the feed tonuget.configwith a mapping instead.
- Named mutexes on Linux and macOS are now per user. A named mutex created by one user is no longer visible to processes running as a different user. Applications that share a named mutex across user accounts can restore the previous machine-wide behavior by setting the
- Not remediated: CVE-2026-105016 in the MsQuic library bundled with .NET 6 on Windows. See MsQuic and HTTP/3 in .NET 6 for why it cannot be updated and what we recommend.
.NET 6.0.46 - September 9, 2026
- Version:
6.0.46 - Security fixes in the .NET runtime shared framework — apply to all applications running on the runtime (
Microsoft.NETCore.App):- CVE-2026-66822 An information-disclosure issue in
SocketsHttpHandlerwhere theProxy-Authorizationheader was kept when following a redirect, so proxy credentials could be sent on to the redirect target; the header is now cleared on redirect, alongsideAuthorization. - CVE-2026-69439 An out-of-bounds write in the Windows-only
Microsoft.DiaSymReader.Nativecomponent carried by the shared framework, wherePortablePDB::ComposeSrcInfotruncated a 64-bit length to 32 bits and wrote past the end of a native heap allocation while parsing a crafted Portable PDB; the component is updated to the fixed build. - CVE-2026-69522 An out-of-bounds write in the same component, where
EnumC13Lines::getLinesColumnscomputed an oversizedmemcpylength and wrote past the end of its destination buffer while processing a crafted PDB; the component is updated to the fixed build. - CVE-2026-71328 A heap out-of-bounds write in the same component, where
PSGSI1::readAddrMapsuffered an integer wrap while reading the address map of an MSFZ-format PDB and sized its write from the wrapped value; the component is updated to the fixed build.
- CVE-2026-66822 An information-disclosure issue in
- Security fixes in the .NET SDK's bundled build tooling — apply to the
dotnetCLI and build operations (all SDK users); the runtime that applications execute on is unaffected:- CVE-2026-58649 An information-disclosure issue in the
dotnet watchbrowser refresh server, where the WebSocket endpoint accepted an upgrade from any origin, so a page on an attacker-controlled site could connect to a developer's local refresh server and read the IL and PDB payloads pushed over it; the endpoint now checks theOriginheader against an allow-list of local hosts and rejects anything else.
- CVE-2026-58649 An information-disclosure issue in the
.NET 6.0.45 - August 18, 2026
- Version:
6.0.45 - Security fixes in the .NET runtime shared framework — apply to all applications running on the runtime (
Microsoft.NETCore.App):- CVE-2025-30399 A remote-code-execution issue in the .NET native host where, for an application carrying no
.deps.json, the runtime library path was composed from an empty application directory in component-hosting mode, leaving a relative path that the platform loader resolved through its ambient search order including the current working directory; the fallback no longer runs in component-hosting mode, and every host library load now requires a rooted path. - CVE-2025-55248 An information-disclosure issue in
System.Net.Mailwhere an asynchronous send withEnableSslset continued over an unencrypted connection when the server rejectedEHLO, becauseSTARTTLSis advertised only in theEHLOresponse; the asynchronous path now fails closed, matching the synchronous one.
- CVE-2025-30399 A remote-code-execution issue in the .NET native host where, for an application carrying no
- Security fixes in Kestrel's HTTP/3 support — apply only to applications that have enabled HTTP/3 on a Kestrel listener (
Microsoft.AspNetCore.App):- CVE-2025-26682 A denial-of-service in HTTP/3 control-stream handling where the full declared length of a frame was buffered before the frame was processed, so a peer could hold a large and growing allocation with very little traffic; an oversized control-stream frame is now rejected as soon as its declared length can be read.
- Security fixes in the .NET SDK's bundled build tooling — apply to the
dotnetCLI and build operations (all SDK users); the runtime that applications execute on is unaffected. The SDK now bundlesMicrosoft.Build.*17.3.4.1:- CVE-2025-26646 A spoofing issue in the MSBuild
DownloadFiletask where the output filename was taken from the response'sContent-Dispositionheader rather than from the requested address, letting the responding server rename the download and so overwrite an existing file in the destination folder; the name is now derived from the request. - CVE-2025-55247 A denial-of-service on Linux where MSBuild created its temporary directory at a path derived from the user name, so any other local user could predict that path and create it first; the directory is now created with an unpredictable name and owner-only permissions.
- CVE-2025-26646 A spoofing issue in the MSBuild
.NET 6.0.44 - August 13, 2026
- Version:
6.0.44 - Security fixes in the .NET runtime shared framework — apply to all applications running on the runtime (
Microsoft.NETCore.App):- CVE-2026-62901 A denial-of-service in WebSocket permessage-deflate decompression (
System.Net.WebSockets) where a message terminated with a BFINAL final block left compressed bytes unconsumed, so the inflater made no forward progress and the receive loop never completed; such messages are now rejected. - CVE-2026-62909 An information-disclosure and elevation-of-privilege issue on Linux where a failure to generate the diagnostics IPC socket name left the socket bound to the abstract namespace, which carries no filesystem permissions and is reachable by any process in the same network namespace; name-generation failure is now fatal instead.
- CVE-2026-62899 A request-smuggling issue in the managed
HttpListener(non-Windows only) where aContent-Lengthabovelong.MaxValuewas silently treated as0rather than rejected, desynchronising the request body boundary from what a front-end proxy computed; the header is now parsed strictly and invalid values fail the request.
- CVE-2026-62901 A denial-of-service in WebSocket permessage-deflate decompression (
- Security fixes in Windows Presentation Foundation (WPF) — apply to WPF desktop applications on Windows (
Microsoft.WindowsDesktop.App):- CVE-2026-62871 An elevation-of-privilege issue in the TrueType font subsetter where character-map and embedded-bitmap table offsets and counts were used without bounds validation, allowing a crafted font to drive a heap out-of-bounds write; the subsetter now validates those tables before use.
- CVE-2026-62886 An elevation-of-privilege issue in glyph-run geometry generation (
CGlyphRunGeometrySink) where an integer overflow in a size calculation produced an undersized allocation and a subsequent heap out-of-bounds write; the arithmetic is now overflow-checked. - CVE-2026-62897 A remote-code-execution issue in glyph-run geometry generation (
CGlyphRunGeometrySink) arising from the same class of unchecked integer arithmetic on a separate path; that path is now overflow-checked as well. - CVE-2026-70354 A remote-code-execution issue in the pixel-shader bytecode translator where a
NOPinstruction was not handled in the pass that sizes the instruction buffer, so a shader with a parameter-style token after aNOPwas counted short and the decode pass wrote past the buffer; such shaders are now rejected. - CVE-2026-62902 An information-disclosure issue in XPS document handling where resource loading was not confined to the containing package, so a crafted document could cause outbound requests to attacker-chosen locations (server-side request forgery) and could send default credentials with them; resource loading is now scoped to its own package and default credentials are no longer supplied.
.NET 6.0.43 - July 16, 2026
- Version:
6.0.43 - Security fixes in the .NET runtime shared framework — apply to all applications running on the runtime (
Microsoft.NETCore.App):- CVE-2026-50651 A denial-of-service (out-of-memory) in the HTTP/2 client (
System.Net.Http) where a malicious server can flood a connection with SETTINGS/PING frames faster than the client acknowledges them, growing an unbounded internal write queue; the client now caps the number of outstanding fire-and-forget frames and aborts the connection when the limit is exceeded. - CVE-2026-50659 An SMTP smuggling / spoofing issue in
System.Net.Mailwhere a deferred trailing carriage return could split message content across writes; dot-stuffing is now applied correctly across buffer boundaries. - CVE-2026-50528 A security-feature-bypass in
System.Net.SecurityNegotiateStream where Extended Protection support was not enforced on Unix; the support check now fails closed. - CVE-2026-57108 A denial-of-service in X.509 certificate name parsing (
System.Security.Cryptography.X509Certificates,GetX509NameInfo) caused by ASN.1 type confusion in UPNotherNamesubject alternative names; the parser now validates the ASN.1 type.
- CVE-2026-50651 A denial-of-service (out-of-memory) in the HTTP/2 client (
- Security fixes in the opt-in
System.Security.Cryptography.Xmlpackage — apply only to applications that reference it:- CVE-2026-47302 A denial-of-service in XML encryption processing where an unbounded transform chain could be abused; the transform-chain length is now capped.
- CVE-2026-47304 A security-feature-bypass where
SignedXmlaccepted truncated HMAC signatures; truncated HMAC signatures are now rejected by default. - CVE-2026-50525 A denial-of-service in XML decryption where the number of decrypted
EncryptedDataelements was unbounded; a configurable cap is now enforced. - CVE-2026-50527 A denial-of-service where a
+character in a cryptographic algorithm type name could be abused; such names are now rejected. - CVE-2026-50648 A denial-of-service caused by transform state retained across an XML transform chain; transform state is now released across the chain.
- Security fixes in the opt-in
Microsoft.AspNetCore.Authentication.Negotiatepackage — apply only to applications that reference it:- CVE-2026-47300 An elevation-of-privilege in the Negotiate LDAP adapter where a principal from a foreign realm could be resolved against a same-named local account; claims retrieval now verifies the principal's realm against the configured LDAP domain (and escapes LDAP filter values).
- CVE-2026-47303 An LDAP identifier-confusion issue (CN vs. sAMAccountName) in the Negotiate LDAP adapter; groups are now resolved by distinguished name, with nested-group cycle detection to prevent unbounded recursion.
- Security fixes in Windows Presentation Foundation (WPF) — apply to WPF desktop applications:
- CVE-2026-50646 A remote code execution vulnerability in WPF XAML parsing.
- CVE-2026-50649 A remote code execution vulnerability in WPF XAML parsing.
- CVE-2026-50650 An elevation-of-privilege vulnerability in WPF XAML parsing.
.NET 6.0.42 - June 27, 2026
- Version:
6.0.42 - Security fixes in the .NET SDK's bundled build tooling — apply to the
dotnetCLI and build/restore/pack operations (all SDK users); the runtime that applications execute on is unaffected:- GHSA-g4vj-cjjj-v7hg A defense-in-depth fix in the NuGet client bundled with the SDK that validates a downloaded package's identity (ID and version) against the requested package, preventing a compromised or misconfigured feed from serving a different package than requested.
- CVE-2024-43485 The System.Text.Json assembly bundled with the SDK was updated
6.0.0→6.0.11, addressing a deserialization denial-of-service. (The in-box System.Text.Json in the runtime shared framework — which applications use at runtime — was already patched in earlier releases and is unchanged in 6.0.42.)
- Dependency security updates in opt-in ASP.NET Core add-on packages — apply only to applications that reference the listed package:
Microsoft.AspNetCore.SignalR.Protocols.MessagePack— bundledMessagePackupdated2.1.90→2.5.301:- CVE-2024-48924 A vulnerability in the MessagePack library where deserializing deeply nested untrusted data can cause a stack overflow, allowing an unauthorized attacker to deny service.
- The update to MessagePack
2.5.301additionally resolves the following MessagePack advisories (all fixed in2.5.301): CVE-2026-48109, CVE-2026-48506, CVE-2026-48509, CVE-2026-48510, CVE-2026-48511, CVE-2026-48512, CVE-2026-48513, CVE-2026-48514, CVE-2026-48515, CVE-2026-48516, CVE-2026-48517.
Microsoft.Extensions.Caching.SqlServerand thedotnet-sql-cachetool — bundledMicrosoft.Data.SqlClientupdated2.1.7→5.2.2(which pulls patchedAzure.Identity1.10.2→1.11.4):- CVE-2024-35255 A vulnerability in the Azure Identity library for .NET where improper handling of local resources can allow an authenticated attacker to elevate privileges locally.
- CVE-2024-29992 An information disclosure vulnerability in the Azure Identity library for .NET that can expose sensitive information to an attacker.
- Note:
Microsoft.Data.SqlClient5.x defaults connection encryption toEncrypt=true; connection strings targeting a server without a trusted TLS certificate may needEncrypt=FalseorTrustServerCertificate=True.
Microsoft.AspNetCore.SignalR.StackExchangeRedisandMicrosoft.AspNetCore.DataProtection.StackExchangeRedis— bundledStackExchange.Redisupdated2.2.4→2.7.27(end-of-life dependency moved to a supported, security-maintained version).
.NET 6.0.41 - June 10, 2026
- Version:
6.0.41 - Security fixes for the following CVEs:
- CVE-2026-32177 A heap-based buffer overflow vulnerability in .NET can allow an unauthorized attacker to elevate privileges locally.
- CVE-2026-35433 A vulnerability in .NET can allow an unauthorized attacker to elevate privileges locally.
- CVE-2026-45490 An improper authorization vulnerability in .NET can allow an authorized attacker to elevate privileges locally.
- CVE-2026-45591 An uncontrolled resource consumption vulnerability in ASP.NET Core can allow an unauthorized attacker to deny service over a network.
.NET 6.0.40 - April 14, 2026
- Version:
6.0.40 - Security fixes for the following CVEs:
- CVE-2026-32178 A vulnerability in System.Net.Mail where specially crafted email address data can be used to perform a spoofing attack over the network
- CVE-2026-26171 A vulnerability in System.Security.Cryptography.Xml where EncryptedXml processing can trigger uncontrolled resource consumption, allowing an attacker to deny service over the network
- CVE-2026-32203 A vulnerability in System.Security.Cryptography.Xml where a buffer overflow in EncryptedXml processing can be triggered by specially crafted input, allowing an attacker to deny service over the network
- CVE-2026-33116 A vulnerability in System.Security.Cryptography.Xml where EncryptedXml processing can be driven into an infinite loop, allowing an attacker to deny service over the network
.NET 6.0.39 - October 17, 2025
- Version:
6.0.39 - Security fixes for the following CVEs:
- CVE-2025-55315 A vulnerability that involves inconsistent interpretation of HTTP requests in ASP.NET Core and Microsoft.AspNetCore.Server.Kestrel.Core, enabling a sophisticated attack known as HTTP Request Smuggling
.NET 6.0.38 - June 4, 2025
- Version:
6.0.38 - Security fixes for the following CVEs:
- CVE-2025-7326 A vulnerability exists in applications using ASP.NET and the Microsoft.AspNetCore.Identity Nuget Package when calling
RefreshSignInAsyncwith an improperly authenticated user parameter that could allow an attacker to sign into another user's account, resulting in Elevation of Privilege. - CVE-2025-24070 A vulnerability exists in applications using ASP.NET and the Microsoft.AspNetCore.Identity Nuget Package when calling
RefreshSignInAsyncwith an improperly authenticated user parameter that could allow an attacker to sign into another user's account, resulting in Elevation of Privilege. - CVE-2025-21176 A vulnerability exists in
DiaSymReader.dlldue to buffer over-read. Insufficient input validation in Visual Studio allows remote code execution via crafted files. An attacker could exploit this vulnerability by loading a maliciously crafted file in Visual Studio. - CVE-2025-21173 A vulnerability exists in the .NET SDK as a result of insecure temporary file usage on Linux that allows local system privilege escalation by attackers.
- CVE-2025-21172 A vulnerability exists in
msdia140.dlldue to integer overflow and heap-based overflow. Exploitation of this vulnerability requires that an attacker convince a user to open a maliciously crafted package file in Visual Studio. - CVE-2024-38229 A vulnerability exists in ASP.NET when closing an HTTP/3 stream while application code is writing to the response body, a race condition may lead to use-after-free, resulting in Remote Code Execution.
- CVE-2024-35264 A vulnerability exists in ASP.NET Core where Data Corruption in Kestrel HTTP/3 can result in remote code execution.
- CVE-2025-7326 A vulnerability exists in applications using ASP.NET and the Microsoft.AspNetCore.Identity Nuget Package when calling