PoC and Full Details Released for macOS autofs Flaws Enabling Root Code Execution and Gatekeeper Bypass
Do Son 
TL;DR
Researcher Mr.Gedik has published a full write-up and proof-of-concept harness for CVE-2026-84568 and CVE-2026-84570, two macOS autofs vulnerabilities. The first lets an attacker who controls a network directory server run code as root on Macs. The second allows a Gatekeeper bypass, and Apple fixed both on September 14, 2026.
- Product: Apple macOS
- Vulnerabilities: 2 flaws (CVE-2026-84568, CVE-2026-84570)
- Highest severity: 7.8 (High · CVSSv3)
- Status: No confirmed exploitation yet; patches available
- Action: Update to 15.8, 26.7, 27 now
| CVE | CVSS (CVSSv3) | Fixed in | Status |
|---|---|---|---|
| CVE-2026-84568 | 7.8 | 15.8, 26.7, 27 | Not exploited |
| CVE-2026-84570 | 4.4 | 15.8, 26.7, 27 | Not exploited |
Why It Matters
Many companies bind their Macs to LDAP or Open Directory and let autofs mount network home folders. That convenience turns directory data into a control channel. If an attacker gains write access to the directory, every Mac that reads it becomes a potential target.
CISA’s enrichment in the CVE records scores the root flaw CVSS 7.8 and the Gatekeeper flaw 4.4. However, the public code makes both easier to test, and unpatched enterprise fleets remain exposed.
Details and PoC are public
The CVE-2026-84568 research repository on GitHub includes source analysis, a Python harness and on-host validators. The researcher says the validators all returned “PASS” on an affected macOS 26.4 lab host. The repository is meant only for “an isolated, authorized lab containing an intentionally unpatched Mac.”
How the Attack Works
CVE-2026-84568: root code execution
Autofs reads map entries that name a filesystem type and mount options. The vulnerable code built a mount helper path by joining a fixed prefix with that filesystem type. As a result, a crafted value could escape the helper folder and point at a binary delivered over NFS. The privileged automountd process then launched it.
A lookup still has to trigger the chain. The write-up stresses that “creating a record does not execute it by itself.” A root-originating lookup yields root execution, while a user lookup runs code in that user’s context.
CVE-2026-84570: Gatekeeper bypass
The second macOS autofs vulnerability let directory-supplied options cancel the default nodev protection. The resulting NFS mount also lacked noexec and quarantine flags. In testing, Gatekeeper rejected an ad-hoc signed app on explicit check. Yet macOS still launched the same app from the NFS mount “without an approval step.”
The researcher also showed that device files on such a mount bypassed normal access checks. Apple’s own security content for macOS Golden Gate 27 lists both flaws under autofs.
Exploitation status
A public proof-of-concept exists. However, no source reports attacks in the wild, and neither CVE is in CISA’s KEV catalog.
Affected Versions
- macOS Sequoia before 15.8
- macOS Tahoe before 26.7
- Releases before macOS Golden Gate 27
Patch and Mitigation Steps
- Update to macOS Sequoia 15.8, Tahoe 26.7 or Golden Gate 27.
- Restrict who can change automount maps and home directory attributes in LDAP or Open Directory.
- Log and alert on directory changes that add path characters or a “dev” option to automount entries.
- Watch for automountd child processes running outside Apple’s mount helper folder.
- Flag unexpected NFS mounts under /home.
Directory controls reduce exposure, but they do not replace patching. Admins who manage directory-bound Macs should treat these macOS autofs vulnerabilities as a priority, given the public Gatekeeper bypass research.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!
Buy Me a Coffee
