Protected-data disclosure via flawed AppSandbox file handling
Published Dec 12, 2025 · Updated Dec 12, 2025
Authorization bypass in AppSandbox in Apple macOS 14 before 14.8.3, 15 before 15.7.3, and 26 before 26.2 allows local users to read protected data. Apple identifies a file-handling logic error in AppSandbox but has not disclosed the affected file operation or validation failure. Execution of a local app and user interaction are required; the reported consequence is limited to protected-data disclosure.
Summary
What happened
Authorization bypass in AppSandbox in Apple macOS 14 before 14.8.3, 15 before 15.7.3, and 26 before 26.2 allows local users to read protected data. Apple identifies a file-handling logic error in AppSandbox but has not disclosed the affected file operation or validation failure. Execution of a local app and user interaction are required; the reported consequence is limited to protected-data disclosure.
The record
- CVE
- CVE-2025-46289
- Published
- Dec 12, 2025
- Updated
- Dec 12, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-285, T1005
- Attack vector
- local
- Privileges
- unauthenticated
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 <14.8
- Affected versionversion=unspecified <15.7
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.
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