Code execution via WebKit memory corruption
Published Jan 23, 2024 · Updated Apr 2, 2026
Memory corruption in WebKit in Apple iOS, iPadOS, and macOS allows remote attackers to execute code through malicious web content. Apple has not disclosed the affected WebKit routines or the specific unsafe memory operations performed while processing the content. Exploitation requires the target to process attacker-controlled web content and results in code execution in the WebKit process context.
Summary
What happened
Memory corruption in WebKit in Apple iOS, iPadOS, and macOS allows remote attackers to execute code through malicious web content. Apple has not disclosed the affected WebKit routines or the specific unsafe memory operations performed while processing the content. Exploitation requires the target to process attacker-controlled web content and results in code execution in the WebKit process context.
The record
- CVE
- CVE-2024-23214
- Published
- Jan 23, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2024CVE 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 <16.7.5
- Affected versionversion=0 <17.3
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.
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