CVE-2026-85370 in Windowsinfo

Summary

by MITRE • 10/14/2026

Use after free in WebDAV allows an authorized attacker to elevate privileges locally.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 10/14/2026

The vulnerability described involves a use-after-free error within the Web Distributed Authoring and Versioning protocol implementation, specifically affecting systems where local privilege escalation is possible for authenticated users. This class of software defect occurs when a program continues to use a pointer after the memory it points to has been freed or reallocated. In the context of network services like WebDAV, which facilitates file management over HTTP, such flaws can be particularly dangerous because they allow an attacker who already possesses valid credentials on the local system to manipulate memory states in ways that bypass standard security controls. The core technical flaw lies in the lifecycle management of data structures associated with WebDAV requests or responses. When a request is processed, specific buffers or objects are allocated in memory to handle metadata, headers, or file paths. If the application fails to properly nullify pointers after deallocation or if it accesses these regions during subsequent operations that assume the original allocation still exists, an attacker can exploit this window of opportunity. By carefully crafting inputs that trigger premature freeing followed by access, the attacker gains control over how the program interprets memory contents, potentially leading to arbitrary code execution with elevated privileges.

From a technical perspective, use-after-free vulnerabilities are categorized under CWE-416 in the Common Weakness Enumeration framework. This weakness represents a critical failure in resource management where the application does not verify that allocated resources remain valid before accessing them. In operating systems and server applications, memory corruption of this nature often leads to undefined behavior, which security researchers leverage to overwrite function pointers or return addresses on the stack. For WebDAV services running with administrative privileges or integrated into enterprise directory structures, such a flaw can allow an authenticated user to execute code in the context of the service account. This effectively transforms a low-privilege local account into one with system-level access, enabling the installation of malware, creation of backdoors, or exfiltration of sensitive data stored on the server. The impact is severe because it undermines the fundamental principle of least privilege and allows lateral movement within an organization's network infrastructure once initial foothold is established through legitimate credentials.

The operational impact extends beyond simple code execution to include potential denial of service conditions if the memory corruption causes crashes or instability in the WebDAV service. However, the primary concern remains the elevation of privileges. An attacker leveraging this vulnerability can bypass authentication mechanisms for higher-level functions, modify system configurations, and access restricted files that are normally protected by operating system permissions. This aligns with several tactics identified in the MITRE ATT&CK framework, particularly those related to privilege escalation such as T1068 Exploitation for Privilege Escalation or T1548 Abuse Elevation Control Mechanism if specific configuration controls are manipulated via the elevated access. The presence of this vulnerability indicates a significant gap in input validation and memory safety practices within the software development lifecycle, suggesting that rigorous static analysis and dynamic testing were either insufficient or absent during the creation of the affected component.

Mitigation strategies must focus on both immediate remediation and long-term architectural improvements. Immediately, organizations should apply vendor-provided patches that address the specific use-after-free condition by ensuring proper pointer nullification after memory deallocation and validating object lifecycles before access. If patching is not immediately feasible, restricting network access to WebDAV services to only trusted IP ranges can reduce exposure, although this does not mitigate risks from authenticated local attackers. Long-term solutions involve adopting secure coding practices that prevent such memory errors, such as using safe programming languages with automatic garbage collection or implementing rigorous code review processes focused on resource management. Additionally, deploying runtime application self-protection tools and enabling strict access controls like SELinux or AppArmor can limit the damage caused by successful exploitation attempts. Regular vulnerability scanning and penetration testing should be conducted to identify similar flaws in other network-facing services before they can be exploited in production environments.

Responsible

Microsoft

Reservation

09/03/2026

Disclosure

10/14/2026

Moderation

accepted

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!