CVE-2026-65810: Microsoft .NET Framework relative path traversal privilege escalation

CVE-2026-65810 · Severity: high · CVSS 7.8 · Published 2026-08-11

The .NET Framework, a core runtime used by millions of Windows applications, contains a relative path traversal vulnerability that allows an unprivileged attacker to gain elevated system privileges on a local machine. Exploitation requires local access but no special preconditions, potentially allowing an attacker to take complete control of the system and access sensitive data or functionality.

Technologies: Microsoft .NET Framework. Vendors: Microsoft.

Quick answers

Is CVE-2026-65810 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-65810 being exploited in the wild.
How severe is CVE-2026-65810?
High severity, with a CVSS score of 7.8, published 11 August 2026.
Which products and versions are affected?
Microsoft .NET Framework.
Is there a fix for CVE-2026-65810?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-65810 attacked?
It is attacked with local access.
Am I affected by CVE-2026-65810?
Check whether you run Microsoft .NET Framework. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A relative path traversal vulnerability in the .NET Framework permits local privilege escalation when the framework resolves file paths using insufficient validation. The vulnerability is triggered through local attack vector; an attacker with standard user privileges can exploit inadequate path handling to access or execute code with elevated privileges. The precise vulnerable component and attack preconditions are not detailed in the available reference material, but the path traversal class suggests the issue stems from improper canonicalization of relative file paths. Patches are expected to be available through Microsoft's standard security update channels.

Affected products

  • Microsoft .NET Framework

Timeline

  • 2026-08-11: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.