Local sandbox escape via quarantine permissions
Published Dec 12, 2025 · Updated Dec 12, 2025
Sandbox escape in macOS Tahoe before 26.1 allows local users to escape an app sandbox through the quarantine component. Apple identifies a permissions issue in quarantine but has not disclosed the faulty permission check or operation that lets the app cross the boundary. Execution of an attacker-controlled sandboxed app is required; escape permits limited access to or modification of resources outside the sandbox without interrupting service.
Summary
What happened
Sandbox escape in macOS Tahoe before 26.1 allows local users to escape an app sandbox through the quarantine component. Apple identifies a permissions issue in quarantine but has not disclosed the faulty permission check or operation that lets the app cross the boundary. Execution of an attacker-controlled sandboxed app is required; escape permits limited access to or modification of resources outside the sandbox without interrupting service.
The record
- CVE
- CVE-2025-43393
- Published
- Dec 12, 2025
- Updated
- Dec 12, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 12, 2025CVE publishedPublication date reported by the CVE source.
- Dec 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <26.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo