Arbitrary code execution via WebKit memory handling
Published Mar 8, 2024 · Updated Apr 2, 2026
Memory corruption in WebKit across affected Apple operating systems allows remote attackers to execute code via crafted web content. WebKit mishandles memory while processing attacker-controlled page data, but Apple has not published the affected function or exact invalid memory operation. Exploitation requires a user or application to load the content, after which code can run in the WebKit content-processing context.
Summary
What happened
Memory corruption in WebKit across affected Apple operating systems allows remote attackers to execute code via crafted web content. WebKit mishandles memory while processing attacker-controlled page data, but Apple has not published the affected function or exact invalid memory operation. Exploitation requires a user or application to load the content, after which code can run in the WebKit content-processing context.
The record
- CVE
- CVE-2024-23226
- Published
- Mar 8, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 8, 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 <17.4
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