Sensitive-data disclosure via undisclosed permission failure
Published Nov 4, 2025 · Updated Nov 4, 2025
Permissions failure in AppleMobileFileIntegrity in macOS Sequoia before 15.7.2 and Tahoe before 26.1 allows local users to read sensitive data. Apple has not disclosed which permission rule AppleMobileFileIntegrity evaluates incorrectly or how the added restrictions prevent the access. A locally launched app and user interaction are required; the reported consequence is confidential-data exposure, with no reported write or service effect.
Summary
What happened
Permissions failure in AppleMobileFileIntegrity in macOS Sequoia before 15.7.2 and Tahoe before 26.1 allows local users to read sensitive data. Apple has not disclosed which permission rule AppleMobileFileIntegrity evaluates incorrectly or how the added restrictions prevent the access. A locally launched app and user interaction are required; the reported consequence is confidential-data exposure, with no reported write or service effect.
The record
- CVE
- CVE-2025-43378
- Published
- Nov 4, 2025
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-200, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 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 <15.7
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