Protected-file read and write via permission bypass
Published Mar 31, 2025 · Updated Jul 22, 2026
Authorization bypass in AppleMobileFileIntegrity in Apple macOS allows context-dependent attackers to read or write protected files. Apple identifies insufficient permission restrictions in AppleMobileFileIntegrity but has not disclosed the failed authorization check or code path. Execution of a malicious app on an affected Mac is required; the bounded consequence is unauthorized reading or modification of protected files.
Summary
What happened
Authorization bypass in AppleMobileFileIntegrity in Apple macOS allows context-dependent attackers to read or write protected files. Apple identifies insufficient permission restrictions in AppleMobileFileIntegrity but has not disclosed the failed authorization check or code path. Execution of a malicious app on an affected Mac is required; the bounded consequence is unauthorized reading or modification of protected files.
The record
- CVE
- CVE-2025-24233
- Published
- Mar 31, 2025
- Updated
- Jul 22, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-863, T1565.001, T1005
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 31, 2025CVE publishedPublication date reported by the CVE source.
- Jul 22, 2026Record 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=0 <13.7.5
- Affected versionversion=0 <14.7.5
- Affected versionversion=0 <15.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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