Arbitrary code execution via WebKit memory handling
Published Feb 10, 2025 · Updated Jun 3, 2026
A memory-handling flaw in WebKit across affected Apple platforms allows remote attackers to execute arbitrary code via crafted web content. Apple identifies improved memory handling and WebKit Bugzilla 263001 but does not disclose the faulty function or operation. Exploitation requires processing attacker-controlled web content and user interaction, after which code executes in the WebKit content-processing context.
Summary
What happened
A memory-handling flaw in WebKit across affected Apple platforms allows remote attackers to execute arbitrary code via crafted web content. Apple identifies improved memory handling and WebKit Bugzilla 263001 but does not disclose the faulty function or operation. Exploitation requires processing attacker-controlled web content and user interaction, after which code executes in the WebKit content-processing context.
The record
- CVE
- CVE-2024-27859
- Published
- Feb 10, 2025
- Updated
- Jun 3, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-94, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2025CVE publishedPublication date reported by the CVE source.
- Jun 3, 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.
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