App termination and process-memory corruption via video parsing
Published May 12, 2025 · Updated Apr 2, 2026
Improper input validation in CoreMedia across affected Apple platforms allows attackers to crash apps or corrupt process memory via crafted video files. The parser accepts insufficiently sanitized video input, but Apple has not disclosed the specific field, validation failure, or memory operation involved. The file must reach CoreMedia processing; the documented consequence is app termination or process-memory corruption, with no published claim of code execution.
Summary
What happened
Improper input validation in CoreMedia across affected Apple platforms allows attackers to crash apps or corrupt process memory via crafted video files. The parser accepts insufficiently sanitized video input, but Apple has not disclosed the specific field, validation failure, or memory operation involved. The file must reach CoreMedia processing; the documented consequence is app termination or process-memory corruption, with no published claim of code execution.
The record
- CVE
- CVE-2025-31233
- Published
- May 12, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 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.5
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