Safari crash via undisclosed WebKit memory handling
Published Mar 31, 2025 · Updated Jul 22, 2026
Memory handling flaw in WebKit in Safari before 18.4 allows remote attackers to crash Safari by processing malicious web content. Apple identifies WebKit as the affected component but has not disclosed the faulty function or the memory operation performed on untrusted content. The effect is limited to an unexpected browser crash; the same defect affects iOS and iPadOS before 18.4, iPadOS before 17.7.6, macOS before 15.4, tvOS before 18.4, visionOS before 2.4, and watchOS before 11.4.
Summary
What happened
Memory handling flaw in WebKit in Safari before 18.4 allows remote attackers to crash Safari by processing malicious web content. Apple identifies WebKit as the affected component but has not disclosed the faulty function or the memory operation performed on untrusted content. The effect is limited to an unexpected browser crash; the same defect affects iOS and iPadOS before 18.4, iPadOS before 17.7.6, macOS before 15.4, tvOS before 18.4, visionOS before 2.4, and watchOS before 11.4.
The record
- CVE
- CVE-2025-24264
- Published
- Mar 31, 2025
- Updated
- Jul 22, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2025CVE publishedPublication date reported by the CVE source.
- Jul 22, 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.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