Severity by source
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Local attacker already running a sandboxed app (AV:L, PR:L) escapes confinement, crossing a security boundary (S:C) to gain full access to protected resources (C:H/I:H/A:H).
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionCVE.org
An access issue was addressed with additional sandbox restrictions. This issue is fixed in macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.2. An app may be able to break out of its sandbox.
AnalysisAI
Sandbox escape in Apple macOS (Sonoma before 14.8.7, Sequoia before 15.7.7, Tahoe before 26.2) allows a sandboxed application to break out of the App Sandbox and gain broader access to the system, achieving a scope change with total confidentiality, integrity, and availability impact. Apple addressed the underlying access-control weakness with additional sandbox restrictions. There is no public exploit identified at time of analysis, and the EPSS exploitation probability is very low (0.01%).
Technical ContextAI
The affected component is Apple's App Sandbox, the mandatory access control (MAC) layer built on the Seatbelt/sandbox framework that confines applications to a restricted set of file, IPC, and system resource operations. The root cause is classified as CWE-284 (Improper Access Control): the sandbox profile did not sufficiently restrict a resource or operation, allowing a confined app to reach capabilities outside its intended container. Apple's fix tightened the sandbox rules ("additional sandbox restrictions") rather than patching a memory-safety bug. The CPE data identifies the operating system itself (cpe:2.3:o:apple:macos) as the affected product across the Sonoma, Sequoia, and Tahoe release lines.
RemediationAI
Vendor-released patch: update to macOS Sonoma 14.8.7, macOS Sequoia 15.7.7, or macOS Tahoe 26.2, whichever matches the deployed release line, via Software Update or MDM-managed deployment; see Apple's advisory at https://support.apple.com/en-us/125886. Because the flaw resides in the OS sandbox layer there is no meaningful in-product workaround, so patching is the only reliable fix. As interim compensating controls until the update is deployed, restrict installation of untrusted third-party applications, enforce Gatekeeper and notarization requirements, and limit local user privileges so that an attacker is less likely to land the sandboxed foothold needed to attempt the escape - these reduce likelihood but do not remove the underlying weakness.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2025-209797
GHSA-pgh4-8789-8jgp