Memory corruption via crafted web content
Published May 12, 2025 · Updated Apr 2, 2026
Memory corruption in WebKit across affected Apple products allows remote attackers to corrupt process memory via crafted web content. Apple identifies WebKit's memory handling as the locus but has not published the erroneous operation or memory object involved. Processing the crafted content is required; the documented consequence is process-memory corruption, with no published claim of code execution.
Summary
What happened
Memory corruption in WebKit across affected Apple products allows remote attackers to corrupt process memory via crafted web content. Apple identifies WebKit's memory handling as the locus but has not published the erroneous operation or memory object involved. Processing the crafted content is required; the documented consequence is process-memory corruption, with no published claim of code execution.
The record
- CVE
- CVE-2025-24223
- Published
- May 12, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
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?
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