A researcher who goes by Mr.Gedik published a full write-up and proof-of-concept harness on October 26 for two macOS autofs flaws that Apple fixed on September 14. One flaw gives root code execution and the other bypasses Gatekeeper. No exploitation in the wild has been reported.
The account rests on a single outlet’s report.
CVE-2026-84568 Root Execution Through Network Home Folders
CVE-2026-84568, rated CVSS 7.8, lets an attacker who controls a network directory server, using LDAP or Open Directory, run code as root on Macs that mount network home folders through autofs. The companion flaw, CVE-2026-84570, is a Gatekeeper bypass rated CVSS 4.4.
How a Crafted Filesystem Type Escapes the Helper Folder
According to the write-up, the vulnerable code built a mount-helper path by joining a fixed prefix with the filesystem type taken from the map entry. A crafted value escaped the helper folder and pointed at a binary delivered over NFS. The privileged automountd service then launched that binary. A lookup must still trigger the chain.
The GitHub Repository and What It Contains
The repository holds source analysis, a Python harness and on-host validators. The validators all returned PASS on an affected macOS 26.4 lab host. The material is meant for isolated labs with intentionally unpatched Macs.
Exposure Limited to Unpatched Directory-Bound Fleets
No exploitation in the wild has been reported. The report says unpatched enterprise fleets bound to directory services remain exposed, since the attack depends on the Mac using a directory server the attacker controls.
Apple Patched Both Flaws on September 14
Apple fixed both CVE-2026-84568 and CVE-2026-84570 on September 14, 2026. The report advises installing the September 14 macOS updates and tightening write access to directory servers.
What Public Code Changes for Managed Mac Fleets
Public exploit code lowers the barrier for attacking unpatched managed Macs, because attackers no longer need to reconstruct the chain from Apple’s patch. The delay between Apple’s fix and the October 26 release is about six weeks, during which machines that had not installed the update were exposed to anyone able to build their own exploit.
Because the report comes from one outlet, the CVE numbers, severity scores and patch date should be matched with Apple’s security notes and the researcher’s repository.
The exploit requires control of the directory server rather than a foothold on the Mac itself, which keeps the practical risk confined to environments where such control is plausible.
Timeline and Evidence in the Published Write-Up
Apple patched both flaws on September 14, 2026, and the write-up and proof-of-concept harness followed on October 26. The report describes the research as a full write-up and says the repository is intended for isolated labs with intentionally unpatched Macs.
The repository contains three kinds of material: source analysis of the vulnerable code, a Python harness and on-host validators. On an affected macOS 26.4 lab host, all of the validators returned PASS, which the report cites as confirmation that the chain works on an unpatched system.
The two flaws serve different purposes. CVE-2026-84568, rated CVSS 7.8, gives code execution as root. CVE-2026-84570, rated CVSS 4.4, bypasses Gatekeeper, the macOS check on downloaded software. The report does not describe how the two might be combined.
No exploitation in the wild has been reported. The report names unpatched enterprise fleets bound to directory services as the remaining exposure, and recommends installing the September 14 macOS updates and tightening write access to directory servers. A lookup must still trigger the chain, which adds a condition to any attack beyond control of the directory server itself.
The researcher’s repository is aimed at lab validation, and the report says it is meant for isolated environments. The write-up does not describe any attack against a production network, and the report records no exploitation in the wild as of publication.
