Browser crash via faulty WebKit memory handling
Published Jul 29, 2025 · Updated Jul 15, 2026
Memory-handling flaw in WebKit in affected Apple releases allows remote attackers to crash Safari via malicious web content. Apple identifies WebKit Bugzilla issue 292599 but has not disclosed the faulty memory operation or lower-level code locus. User interaction is required to process the content, and the documented consequence is an unexpected browser crash rather than data access or code execution.
Summary
What happened
Memory-handling flaw in WebKit in affected Apple releases allows remote attackers to crash Safari via malicious web content. Apple identifies WebKit Bugzilla issue 292599 but has not disclosed the faulty memory operation or lower-level code locus. User interaction is required to process the content, and the documented consequence is an unexpected browser crash rather than data access or code execution.
The record
- CVE
- CVE-2025-43214
- Published
- Jul 29, 2025
- Updated
- Jul 15, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2025CVE publishedPublication date reported by the CVE source.
- Jul 15, 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.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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