App crash via malformed Model I/O file
Published Jul 29, 2025 · Updated Apr 2, 2026
Improper input validation in Model I/O in Apple iOS, iPadOS, macOS, tvOS, and visionOS allows attackers to crash an app with a crafted file. Apple has not disclosed which Model I/O parser or memory-handling operation fails to validate the file. Exploitation requires Model I/O to process attacker-controlled file content; Apple reports only unexpected app termination, not system compromise or data access.
Summary
What happened
Improper input validation in Model I/O in Apple iOS, iPadOS, macOS, tvOS, and visionOS allows attackers to crash an app with a crafted file. Apple has not disclosed which Model I/O parser or memory-handling operation fails to validate the file. Exploitation requires Model I/O to process attacker-controlled file content; Apple reports only unexpected app termination, not system compromise or data access.
The record
- CVE
- CVE-2025-31281
- Published
- Jul 29, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-20
- Attack vector
- network
- 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