Clarity for AI buildersSponsored by AI Routing
availability

Researcher Details Patched Microsoft Defender for macOS File-Read and Root-Escalation Flaws

Researcher Details Patched Microsoft Defender for macOS File-Read and Root-Escalation Flaws

A researcher reports two patched Microsoft Defender for macOS flaws enabling privileged file access and root escalation.

In a technical writeup published on Spaceraccoon, the researcher describes CVE-2026-50657, an arbitrary file-read vulnerability, and CVE-2026-50658, a local privilege-escalation vulnerability. The author says both were reported to the Microsoft Security Response Center and fixed in the July 2026 Patch Tuesday updates. The supplied evidence contains the researcher's account, not an independent Microsoft advisory or an affected-version list.

The attack chain targeted wdavdaemon, Defender's root-privileged background service. According to the writeup, its two Unix-domain sockets accepted connections from any local process, leaving subsequent identity and authorization checks responsible for restricting sensitive operations. These were local attacks: the described chain began with an unprivileged process already running on the Mac.

A race in caller identification

The researcher found that Defender checked a connecting process's identity using information captured at different times. It retrieved the process ID recorded when the connection began, then looked up the executable path currently associated with that ID and checked its location and signature.

An attacker-controlled process could connect and then execute a legitimate Microsoft-signed Defender binary before the daemon completed its check. The process ID remained the same, but the executable path changed. The daemon could consequently accept a connection initiated by the attacker's program as coming from a trusted Defender component.

This distinction matters because verifying a signed executable is not equivalent to verifying the identity that initiated a request. The writeup recommends macOS audit-token-based validation, which can distinguish process execution generations, rather than relying on a process ID and a later path lookup.

Two privileged operations exposed

For CVE-2026-50657, the researcher used Defender's diagnostic archive function, which the writeup says did not require an additional administrator-authorization check. The root daemon collected files from a user-writable Defender log directory and placed their contents in a world-readable ZIP archive.

A hardlink placed in that directory could make a protected file appear to the collector as an ordinary log file. Unlike a symbolic link, a hardlink passed the regular-file filter described in the research. The root daemon then read the linked file into the archive, exposing its contents to the local user.

The security boundary here was not just the archive's accessibility. It was also the assumption that a regular file found inside a user-controlled directory was safe for a privileged process to collect. The reported behavior illustrates why rejecting symbolic links alone does not address every filesystem-redirection risk.

For CVE-2026-50658, the researcher targeted restoration of quarantined files. According to the writeup, omitting an optional authorization field caused the restore handler to skip its authorization checks; supplying an invalid authorization value instead was correctly rejected. Combined with the caller-identity race, that omission allowed attacker-controlled quarantined content to be restored into a privileged destination.

The file-write capability had an important limit: it could create files but could not overwrite existing ones. The researcher nevertheless reports reaching root execution by creating a normally absent system cron configuration file. That result depended on the described system configuration and should not be read as an unrestricted overwrite capability.

Cross-platform fixes need platform-specific checks

The author compares the findings with earlier Windows Defender vulnerabilities, while saying the macOS flaws were found independently. The central lesson is that similar privileged workflows can fail differently across operating systems: caller identity, authorization APIs and hardlink permissions do not provide interchangeable guarantees.

The source reports fixes but does not identify a minimum corrected Defender build or provide enterprise deployment-verification steps. Administrators therefore cannot determine a particular installation's remediation status from this writeup alone.