Service interruption via malformed HTTP/2 requests
Published Jan 12, 2021 · Updated May 28, 2026
HTTP/2 parsing in Microsoft ASP.NET Core 3.1 through 3.1.10 and 5.0 through 5.0.1 allows remote attackers to interrupt Kestrel. Microsoft identifies Kestrel's HTTP/2 request parser as the locus but has not published the malformed field or incorrect parsing operation. Any network client that can reach an HTTP/2 endpoint can trigger the availability-only condition; affected runtimes can be standalone, included with Visual Studio 2019, or deployed self-contained.
Summary
What happened
HTTP/2 parsing in Microsoft ASP.NET Core 3.1 through 3.1.10 and 5.0 through 5.0.1 allows remote attackers to interrupt Kestrel. Microsoft identifies Kestrel's HTTP/2 request parser as the locus but has not published the malformed field or incorrect parsing operation. Any network client that can reach an HTTP/2 endpoint can trigger the availability-only condition; affected runtimes can be standalone, included with Visual Studio 2019, or deployed self-contained.
The record
- CVE
- CVE-2021-1723
- Published
- Jan 12, 2021
- Updated
- May 28, 2026
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2021CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.0.0 <publication
- Affected versionversion=16.0 <publication
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo