Code execution via WebKit out-of-bounds write
Published Sep 23, 2022 · Updated May 22, 2025
Memory corruption in WebKit in Apple macOS before 12.4 and watchOS before 8.6 allows remote attackers to execute code via crafted web content. The undisclosed WebKit state-management path writes beyond the intended memory buffer while processing untrusted content. Successful exploitation requires a user to process malicious web content and yields code execution in the affected WebKit process.
Summary
What happened
Memory corruption in WebKit in Apple macOS before 12.4 and watchOS before 8.6 allows remote attackers to execute code via crafted web content. The undisclosed WebKit state-management path writes beyond the intended memory buffer while processing untrusted content. Successful exploitation requires a user to process malicious web content and yields code execution in the affected WebKit process.
The record
- CVE
- CVE-2022-26700
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record 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=unspecified <12.4
- Affected versionversion=unspecified <15.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.
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