Skip to content
Microsoft Issues Security Advisory for CVE-2026-70035 Vulnerability

Microsoft Issues Security Advisory for CVE-2026-70035 Vulnerability

First seen 14 Oct 2026, 07:06 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 14, 2026 at 08:29 UTC
  • •CVE-2026-70035 has a CVSS score of 8.8, indicating high severity.
  • •The vulnerability affects Microsoft .NET projects using specific vulnerable package versions.
  • •Developers are urged to update their applications to mitigate risks associated with this flaw.

On October 13, 2026, Microsoft published a security advisory for CVE-2026-70035, a vulnerability in Microsoft.WindowsDesktop.App.Runtime (WPF). This flaw allows for potential remote code execution through unsafe URI fetching and untrusted input handling. Affected systems include.NET projects using specific vulnerable package versions. The CVSS score for this vulnerability is 8.8, categorizing it as high severity. Developers are advised to update their applications to mitigate the risk. The advisory includes guidance on identifying affected packages and updating to secure versions. The vulnerability is linked to CWE-502, which involves deserialization of untrusted data. As of now, there are no reports of in the wild.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-13
CVE-2026-70035 published
Microsoft disclosed a vulnerability in Microsoft.WindowsDesktop.App.Runtime affecting .NET projects.
Advisories.Gitlab

More articles in this cluster (6)

Following this threat?

Track Microsoft and CVE-2026-70035 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions are affected?
The vulnerability affects Microsoft .NET projects that use specific vulnerable package versions listed in the advisory.
Is this being exploited?
Currently, there are no reports of active exploitation in the wild for this vulnerability.
What should developers do?
Developers should update their applications to the latest versions of .NET to mitigate the vulnerability.