In 30 seconds
Security researcher Eugene Lim, who publishes as Spaceraccoon, has gone public with two flaws in Microsoft Defender for Endpoint on macOS, tracked as CVE-2026-50657 and CVE-2026-50658. In his account, a local user with no special rights can read protected files and then run code as root, the most powerful level on a Mac, by abusing sockets that the antivirus's privileged helper daemon leaves open to every local process. He reports both bugs were fixed on July 14, 2026, and that Defender for Mac builds older than 101.26042.0020 are the affected ones.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listspaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
What happened
The privileged component at the center of the story is wdavdaemon, Defender's root-level daemon on macOS. According to the writeup, it exposes two Unix domain sockets, /var/run/wdavdaemon.sock and /var/run/priv_wdavdaemon.sock, both with 0666 permissions, meaning any local process can connect. To decide whether a client is trustworthy, the daemon asks the kernel for the peer's process ID via LOCAL_PEERPID, resolves the executable path with proc_pidpath(), and then checks where that binary lives and whether its code signature is valid.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listspaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source list
That identity check can be beaten with a classic race condition of the TOCTOU family, short for time-of-check-to-time-of-use, where a program verifies one state and then acts on another because things change in between. The researcher describes connecting to the socket, sending a request, and immediately calling execve() to swap his own process for a legitimately signed Defender component under the same process ID. If the daemon resolves the executable path after the swap, it sees a trusted Microsoft binary and approves a request that actually originated in attacker-controlled code.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
The first flaw, CVE-2026-50657, turns a diagnostic feature into an arbitrary file read. A command called get_diagnostic_files bundles logs into a ZIP archive running as root, reportedly with no additional authorization. The trick is to drop a hardlink, a second directory entry pointing at the very same file, to a protected target inside Defender's log directory. Unlike a symlink, a hardlink passes the daemon's regular-file check, so the archive ends up carrying the protected file's contents. The writeup names /etc/kcpassword, local account password hashes, and other secrets as reachable this way.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
The second flaw, CVE-2026-50658, climbs all the way to root. The handle_threat::restore handler moves files out of Defender's quarantine into a directory the caller picks, and when the optional AuthorizationExternalForm field is simply left out of the request, the authorization check is skipped. In the demonstration, a file placed in quarantine had its contents replaced with a cron job, then the restore path created /etc/crontab, a file that normally does not exist on a stock macOS install. Creating it makes launchd start cron, and cron runs each job as the user named in the job, root included, which produced an interactive root shell. The writeup notes two limits: existing files cannot be overwritten, and the restored file's ownership is later set to the original file's owner.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
Why it matters
Endpoint security tools run with deep privileges precisely because they need to touch everything, so a flaw in the protector hands an attacker the very keys it was hired to guard. A local user turning Defender's root daemon into a file-reading and code-execution service inverts the product's purpose.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
The practical blast radius depends on who can reach the machine. The bugs are local, not remote, so the exposed cases are shared or managed Macs, plus any situation where an intruder already holds a low-privilege foothold and wants root. If the reported mechanics hold up, the combination of reading /etc/kcpassword and password hashes plus gaining root would amount to full control of the device and its stored secrets.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listspaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source list
What to do
For teams running Defender for Endpoint on Mac, the reported remedy is a version bump: update to 101.26042.0020 or later. The disclosure says both flaws were fixed on July 14, 2026, so agents patched since that date should already be covered, and older builds are the ones to hunt down fleet-wide.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
No workaround or configuration toggle appears in the batch for teams that cannot update right away, and nothing in the evidence suggests the sockets can be locked down by policy. That leaves inventory and version checks as the main practical action while the update rolls out.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Confirmed and still uncertain
On the ledger of what the researcher reports as settled: the two CVEs map to tracker entries PT-2026-58485 and PT-2026-58486, the attack hinges on world-accessible sockets plus a TOCTOU race in client validation, a proof of concept produced a root shell through /etc/crontab, and fixed builds shipped on July 14, 2026.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
Plenty remains open. The batch carries no report of exploitation in the wild, before or after the patch, no independent reproduction of the findings, and no Microsoft advisory or statement, so real-world severity currently rests on one researcher's analysis. It is also unknown whether other Defender surfaces share the same client-validation pattern.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listspaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source list
What people are saying
The story so far has a single authoritative voice, the researcher's. Eugene Lim laid out the findings in a writeup at spaceraccoon.dev under the title Race Against the Machine, a nod to the timing race at the core of the bypass.spaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
The account ptdbugs amplified the research on X with a step-by-step technical summary, linking the writeup and the dbugs entries for both CVEs along with their PT tracker twins. No other voices, vendor or community, appear in the batch.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Evolution
Public details landed on November 19, 2026, when the writeup, the dbugs news item, and the four tracking pages appeared together in one wave, all carrying the same publication date.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source listspaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source list
The patch is older than the publicity. Per the researcher, fixes shipped on July 14, 2026, so the bugs were corrected quietly and the public only learned of them four months later, a gap during which the specific mechanics stayed out of view.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Reach
2 independent groups, 1 updates, and 0 engagements.
Technical detail
For the implementation-minded, the trust check leans on two calls that can disagree over time. LOCAL_PEERPID reports the process ID captured when the connection is made, while proc_pidpath() resolves whatever binary that PID is running at the moment it is called. The attack lives in the gap: connect and send as the attacker's binary, then execve() into a signed Defender component before the daemon resolves the path, so the check validates a different program than the one that sent the request.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
The file read leans on hardlink semantics. Symlinks to protected files fail the regular-file check, but a hardlink is a genuine directory entry pointing at the same on-disk file and passes, so the root-level ZIP builder follows it straight into protected content with no authorization step in the way.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
The root path leans on optional authorization. handle_threat::restore skips its check entirely when AuthorizationExternalForm is absent, and two constraints shape the exploit: existing files cannot be overwritten, and the restored file's ownership is later set to the original file's owner. Creating a fresh /etc/crontab sidesteps the first limit, and cron's habit of honoring the user named in each job, root included, turns the new file into a root shell.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
Sources and evidence
The evidence base is narrow. The substantive account is the technical summary posted by ptdbugs on X on November 19, 2026, which points to Eugene Lim's writeup on spaceraccoon.dev and to dbugs entries for CVE-2026-50657, CVE-2026-50658 and their PT twins, PT-2026-58485 and PT-2026-58486.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listspaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
Nothing from Microsoft, no advisory, no blog post, and no independent reproduction appears in the batch. Until a vendor confirmation or a second analysis shows up, every claim about the bugs, the proof of concept, and the July 14 fix date should be read as one researcher's account, well documented but single sourced.spaceraccoon.devspaceraccoon.dev · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list



