How severe is CVE-2023-36435?

CVE-2023-36435 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-36435?

CVE-2023-36435 affects the following packages: Microsoft.Native.Quic.MsQuic.OpenSSL (NuGet), Microsoft.Native.Quic.MsQuic.Schannel (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2023-36435?

Update Microsoft.Native.Quic.MsQuic.OpenSSL to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36435 is resolved across your whole dependency graph.

How do I detect CVE-2023-36435 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.Native.Quic.MsQuic.OpenSSL, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-36435 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2023-36435 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-36435 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-36435?

CVE-2023-36435 has an EPSS (Exploit Prediction Scoring System) score of 5.7%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-36435?

CVE-2023-36435 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-36435 published, and has it been updated?

CVE-2023-36435 was published on October 10, 2023 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

CVE-2023-36435 — Microsoft.Native.Quic.MsQ…

HIGHFix: microsoft/msquic@d364fee

CVE-2023-36435 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in Microsoft.Native.Quic.MsQuic.OpenSSL. A fix is available for Microsoft.Native.Quic.MsQuic.OpenSSL — see the affected versions and patch details below.

MsQuic Remote Denial of Service Vulnerability

Also known asBIT-dotnet-2023-36435BIT-dotnet-sdk-2023-36435GHSA-fr44-546p-7xcp

Published

Oct 10, 2023

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-36435.

EPSS Exploitation Probability

via FIRST.org ↗

5.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

.NETMicrosoft.Native.Quic.MsQuic.OpenSSL.NETMicrosoft.Native.Quic.MsQuic.Schannel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The MsQuic server will continue to leak memory until no more is available, resulting in a denial of service.

Patches

The following patch was made:

Fix Memory Leak from Multiple Decodes of TP - https://github.com/microsoft/msquic/commit/d364feeda0dd8b729eca6fef149c1ef98630f0cb

Workarounds

Beyond upgrading to the patched versions, there is no other workaround.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.Native.Quic.MsQuic.OpenSSL`	all versions	2.2.3`dotnet add package Microsoft.Native.Quic.MsQuic.OpenSSL --version 2.2.3`
.NETNuGet	`Microsoft.Native.Quic.MsQuic.Schannel`	all versions	2.2.3`dotnet add package Microsoft.Native.Quic.MsQuic.Schannel --version 2.2.3`

Affected Products

4 products · 4 configurations

Application

.netmicrosoft

≥ 7.0.0 && ≤ 7.0.12

range

windows 11 21h2microsoft

< 10.0.22000.2538

range

windows 11 22h2microsoft

< 10.0.22621.2428

range

windows server 2022microsoft

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.Native.Quic.MsQuic.OpenSSL, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.Native.Quic.MsQuic.OpenSSL to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36435 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact The MsQuic server will continue to leak memory until no more is available, resulting in a denial of service. ### Patches The following patch was made: - Fix Memory Leak from Multiple Decodes of TP - https://github.com/microsoft/msquic/commit/d364feeda0dd8b729eca6fef149c1ef98630f0cb ### Workarounds Beyond upgrading to the patched versions, there is no other workaround.