Memory corruption via crafted audio file processing
Published Jul 29, 2025 · Updated Apr 2, 2026
Memory corruption in CoreAudio across affected Apple platform releases allows attackers to corrupt process memory via a crafted audio file. Apple identifies CoreAudio as the locus and says improved memory handling resolved the issue, but does not disclose the faulty memory operation. Opening or otherwise causing an affected device to process the file is required; the disclosed consequence is memory corruption, and Apple gives no narrower result.
Summary
What happened
Memory corruption in CoreAudio across affected Apple platform releases allows attackers to corrupt process memory via a crafted audio file. Apple identifies CoreAudio as the locus and says improved memory handling resolved the issue, but does not disclose the faulty memory operation. Opening or otherwise causing an affected device to process the file is required; the disclosed consequence is memory corruption, and Apple gives no narrower result.
The record
- CVE
- CVE-2025-43277
- Published
- Jul 29, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2025CVE publishedPublication date reported by the CVE source.
- Apr 2, 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 <18.6
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