CVE-2026-97801Network attack vector

Unauthenticated network tampering

Published Oct 13, 2026 · Updated Oct 13, 2026

Input-validation failure in Microsoft .NET Framework allows remote attackers to tamper with data through network input. The available Microsoft record identifies improper input-type validation but does not disclose the affected component, input format, or faulty operation. Authentication and user interaction are not required; the specific data altered and network exposure configuration remain undisclosed.

CVSS severityUnavailable
Unscored
EPSS probability0.61%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Input-validation failure in Microsoft .NET Framework allows remote attackers to tamper with data through network input. The available Microsoft record identifies improper input-type validation but does not disclose the affected component, input format, or faulty operation. Authentication and user interaction are not required; the specific data altered and network exposure configuration remain undisclosed.

The record

CVE
CVE-2026-97801
Published
Oct 13, 2026
Updated
Oct 13, 2026
Vendor
Microsoft Corporation
Product
Microsoft .NET Framework 3.5 and 4.8.1
Classifications
CWE-1287
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Oct 13, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=4.8.1 <2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Microsoft Corporation · Microsoft .NET Framework 3.5 and 4.8.1version=4.8.1 <2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0
Microsoft Corporation · Microsoft .NET Framework 3.5 and 4.8version=4.8.0 <2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0
Microsoft Corporation · Microsoft .NET Framework 3.5 and 4.7.2version=4.7.0 <2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0
Microsoft Corporation · Microsoft .NET Frameworkversion=3.0.0.0 <2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0; version=4.7.0 <4.7.4150.0; version=4.8.0.0 <4.8.9363.0
Microsoft Corporation · Microsoft .NET Framework 3.5version=3.5.0 <2.0.50727.9188 AND 3.0.30729.9171
Microsoft Corporation · Microsoft .NET Framework 4.8version=4.8.0 <4.8.4811.0

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-1287Improper Validation of Specified Type of Input

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