Skip to main content
CVE-2023-36788VulnerabilityPublished Updated

CVE-2023-36788: Microsoft .NET Framework 3.5 AND 4.8 · Remote Code Execution

Affects Microsoft .NET Framework 3.5 AND 4.8Source CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
NuGetmicrosoft.netframeworkpkg:nuget/microsoft.netframeworkOther threatsAffected
  • =4.8.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement the following specific mitigations: 1) Monitor Microsoft security advisories and apply official patches for .NET Framework 3.5 and 4.8 immediately upon release to remediate the vulnerability. 2) Restrict local access to critical systems by enforcing strict access controls, including least privilege principles and multi-factor authentication for local logins where feasible. 3) Educate users about the risks of social engineering and the importance of cautious interaction with prompts or unexpected application behavior to reduce the likelihood of user interaction exploitation. 4) Employ application whitelisting and endpoint detection and response (EDR) solutions to detect and block anomalous code execution attempts related to .NET Framework processes. 5) Conduct regular audits of systems running .NET Framework to identify and isolate vulnerable versions, prioritizing updates in high-risk environments. 6) Implement network segmentation to limit lateral movement if a system is compromised. 7) Maintain comprehensive logging and monitoring of .NET application activities to enable rapid detection and response to suspicious events. These measures go beyond generic patching by focusing on access control, user awareness, and proactive detection.

Description

.NET Framework Remote Code Execution Vulnerability

References

Community reviews

Loading reviews…