Live › vulnerability › CVE-2026-112504
Go to dashboardA parsing issue in how macOS handles directory paths let an app write to protected parts of the file system. Apple fixed it with stricter path validation in macOS Golden Gate 27.2, Sequoia 15.8.2 and Tahoe 26.7.2.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 21:20 UTC. All times on this page are UTC.
Any Mac running a macOS release older than the fixed versions for its branch. The description says an app must be able to run on the machine, so the risk is local, from software a user has installed or run. Managed fleets that already pin to the fixed builds can skip it.
No product ranges from the sources yet.
sw_vers -productVersion on each Mac and compare against the fixed versions.27.2 (Golden Gate), 15.8.2 (Sequoia) or 26.7.2 (Tahoe) or later, via Software Update.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2. An app may be able to modify protected parts of the file system.
This page as .md · .json · in your agent: get_signal("CVE-2026-112504")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.