CVE-2026-105016
No KEV entry is attached to this observation; this is not evidence that exploitation is absent.
FIRST EPSS: 1.66 % · percentile 76.77 % · scored 7 Nov 2026.
Observed 07 Nov 2026 16:07:52 UTC · Complete immutable risk JSON
No access to your tenant or devices. Every item links to its source. What this means
Heap-based buffer overflow in Microsoft QUIC allows an unauthorized attacker to execute code over a network.
| KB | Type | Restart | Applies to | Known issues | Other CVEs |
|---|---|---|---|---|---|
| KB5126646 | Security Update | Required | Windows Server 2025, Windows Server 2025 (Server Core installation) | MitigatedUsers might be unable to sign in to OWA or send emails on Exchange Server | All CVEs in KB5126646 |
| KB5126653 | Security Update | Required | Windows 11 Version 23H2 for ARM64-based Systems, Windows 11 Version 23H2 for x64-based Systems | None listed | All CVEs in KB5126653 |
| KB5126655 | Security Update | Required | Windows Server 2022, Windows Server 2022 (Server Core installation) | MitigatedUsers might be unable to sign in to OWA or send emails on Exchange Server | All CVEs in KB5126655 |
| KB5127646 | Security Update | Required | Windows 11 Version 26H1 for ARM64-based Systems, Windows 11 version 26H1 for x64-based Systems | None listed | All CVEs in KB5127646 |
| KB5127648 | Security Update | Required | Windows 11 Version 24H2 for ARM64-based Systems, Windows 11 Version 24H2 for x64-based Systems, Windows 11 Version 25H2 for ARM64-based Systems and 3 more | None listed | All CVEs in KB5127648 |
| KB5130034 | Security Update | Required | .NET 8.0 runtime installed on Windows | None listed | All CVEs in KB5130034 |
| KB5130035 | Security Update | Required | .NET 9.0 runtime installed on Windows | None listed | All CVEs in KB5130035 |
Microsoft Patch Tuesday for October 2026 — Snort rules and prominent vulnerabilities · 13 Oct 2026
Talos supplies analysis and cycle-level Snort rule references. Its article does not map each rule to a CVE or establish protection for your deployment. MSRC remains the source for vulnerability and fixing-update facts.
Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.
Cite this versionUp to 100 recent field edits are shown; older edits may be outside retention.
Explore global source statements, affected packages and advisory history for CVE-2026-105016. The catalog has a separate collection scope from Microsoft release records.
CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No KEV entry is attached to this observation; this is not evidence that exploitation is absent.
FIRST EPSS: 1.66 % · percentile 76.77 % · scored 7 Nov 2026.
Observed 07 Nov 2026 16:07:52 UTC · Complete immutable risk JSON
Heap-based buffer overflow in Microsoft QUIC allows an unauthorized attacker to execute code over a network.
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Heap-based buffer overflow in Microsoft QUIC allows an unauthorized attacker to execute code over a network.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
datePublished: Oct 13, 2026, 7:01:45 PM
dateUpdated: Oct 31, 2026, 6:13:32 PM
NCSC-2026-0423: Kwetsbaarheden verholpen in Microsoft Windows
CVE-2026-100202 · CVE-2026-100219 · CVE-2026-100222 · CVE-2026-102210 · CVE-2026-105008 · CVE-2026-21413 · CVE-2026-69634 · CVE-2026-69639 · CVE-2026-69705 · CVE-2026-69883 · CVE-2026-69886 · CVE-2026-70024 · CVE-2026-70096 · CVE-2026-70147 · CVE-2026-70153 · CVE-2026-70157 · CVE-2026-70188 · CVE-2026-83517 · CVE-2026-83519 · CVE-2026-83578 · CVE-2026-83693 · CVE-2026-83748 · CVE-2026-83770 · CVE-2026-83780 · CVE-2026-83782 · CVE-2026-83862 · CVE-2026-83869 · CVE-2026-83910 · CVE-2026-83935 · CVE-2026-84015 · CVE-2026-85792 · CVE-2026-85806 · CVE-2026-85809 · CVE-2026-85814 · CVE-2026-85818 · CVE-2026-85844 · CVE-2026-85928 · CVE-2026-88092 · CVE-2026-88102 · CVE-2026-94510 · CVE-2026-96096 · CVE-2026-96219 · CVE-2026-96252 · CVE-2026-96320 · CVE-2026-96864 · CVE-2026-96909 · CVE-2026-96924 · CVE-2026-96934 · CVE-2026-97814 · CVE-2026-97815 · CVE-2026-97816 · CVE-2026-105016
WID-SEC-W-2026-3893: Microsoft Entwicklerwerkzeuge: Mehrere Schwachstellen
CVE-2026-100205 · CVE-2026-102229 · CVE-2026-102231 · CVE-2026-102232 · CVE-2026-102233 · CVE-2026-102234 · CVE-2026-102235 · CVE-2026-102238 · CVE-2026-102851 · CVE-2026-102869 · CVE-2026-102870 · CVE-2026-103572 · CVE-2026-105016 · CVE-2026-105729 · CVE-2026-105732 · CVE-2026-108398 · CVE-2026-109468 · CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69370 · CVE-2026-69651 · CVE-2026-70007 · CVE-2026-70035 · CVE-2026-70098 · CVE-2026-70159 · CVE-2026-70161 · CVE-2026-70162 · CVE-2026-70165 · CVE-2026-70174 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70190 · CVE-2026-70194 · CVE-2026-70196 · CVE-2026-70197 · CVE-2026-83520 · CVE-2026-84008 · CVE-2026-85363 · CVE-2026-85790 · CVE-2026-87697 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96224 · CVE-2026-96225 · CVE-2026-96229 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96232 · CVE-2026-96233 · CVE-2026-96234 · CVE-2026-96235 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96251 · CVE-2026-96303 · CVE-2026-96957 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960 · CVE-2026-97788 · CVE-2026-97801
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 3.1 · 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Heap-based buffer overflow in Microsoft QUIC allows an unauthorized attacker to execute code over a network.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Undergoing Analysis
Weakness classifications: CWE-122
published: 2026-10-13T19:17:57.750
lastModified: 2026-10-22T22:17:52.370
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · [email protected] · Secondary · 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
## Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in Microsoft QUIC as used by .NET 8.0, .NET 9.0, .NET 10.0, and .NET 11 RC2 on Windows. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A crafted IPv6 QUIC packet can reach the Microsoft QUIC HTTP/3 path without authentication or user interaction and trigger remote code execution. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/446 ## CVSS Details - **Version:** 3.1 - **Severity:** Critical - **Score:** 9.8 - **Vector:** `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` - **Weakness:** CWE-122 (Heap-based Buffer Overflow) ## Affected Platforms - **Platforms:** Windows - **Architectures:** All ## <a name="affected-packages"></a>Affected Packages The vulnerability affects Microsoft .NET projects that use an affected package version listed below. Package name | Affected version | Patched version ------------ | ---------------- | --------------- [Microsoft.Native.Quic.MsQuic.Schannel](https://www.nuget.org/packages/Microsoft.Native.Quic.MsQuic.Schannel) | >= 2.5.11-ci.156755675, <= 2.5.11-ci.156755675 | 2.5.11-ci.159417053 ## Advisory FAQ ### <a name="how-affected"></a>How do I know if I am affected? If your application uses a package version listed in [affected packages](#affected-packages), it is exposed to the vulnerability. ### <a name="how-fix"></a>How do I fix the issue? 1. Install the latest servicing update for your supported .NET release. 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. 2. If your application directly references `Microsoft.Native.Quic.MsQuic.Schannel`, update the package reference to version 2.5.11-ci.159417053 or later. You can list the .NET versions installed on your system by running the `dotnet --info` command. Once you have installed the updated runtime or SDK, restart your applications for the update to take effect. Additionally, if you have deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) 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](https://msrc.microsoft.com/report/vulnerability/new). Further information can be found in the MSRC [Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue). 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 repositories are located at https://github.com/dotnet/runtime. The Announcements repository (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 [CVE-2026-105016](https://www.cve.org/CVERecord?id=CVE-2026-105016) ### Acknowledgements pwn2addr ### Revisions V1.0 (10/13/2026): Advisory published.
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Publisher rating · CRITICAL