Sandbox escape with arbitrary file access
Published Sep 15, 2025 · Updated Sep 15, 2025
Improper access control in IDE CoreML in Apple Xcode before 26 allows local users to read and write files outside the app sandbox. Apple states only that improved checks addressed the issue and has not disclosed the specific IDE CoreML validation failure or file-access path. Exploitation requires a local app to be run by a user; successful abuse bypasses sandbox boundaries for file confidentiality and integrity.
Summary
What happened
Improper access control in IDE CoreML in Apple Xcode before 26 allows local users to read and write files outside the app sandbox. Apple states only that improved checks addressed the issue and has not disclosed the specific IDE CoreML validation failure or file-access path. Exploitation requires a local app to be run by a user; successful abuse bypasses sandbox boundaries for file confidentiality and integrity.
The record
- CVE
- CVE-2025-43263
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- Apple
- Product
- Xcode
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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
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