Unauthenticated denial of service via out-of-bounds write
Published Oct 13, 2026 · Updated Oct 13, 2026
Out-of-bounds write in Microsoft ASP.NET Core allows remote attackers to interrupt application service over a network. The public record does not identify the affected function, the triggering input, or the operation that writes beyond the buffer boundary. Authentication and user interaction are not required; the disclosed consequence is service interruption, with crash versus hang unspecified.
Summary
What happened
Out-of-bounds write in Microsoft ASP.NET Core allows remote attackers to interrupt application service over a network. The public record does not identify the affected function, the triggering input, or the operation that writes beyond the buffer boundary. Authentication and user interaction are not required; the disclosed consequence is service interruption, with crash versus hang unspecified.
The record
- CVE
- CVE-2026-96233
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- Microsoft Corporation
- Product
- Microsoft .NET Framework 3.5 and 4.8.1
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 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=4.8.1 <2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started