Remote WebKit process crash
Published Sep 15, 2025 · Updated Sep 15, 2025
Memory corruption in Apple WebKit before 26 allows remote attackers to crash a process by supplying maliciously crafted web content. Apple identifies WebKit Bugzilla 296490 but has not published the faulty function or memory operation, stating only that improved memory handling resolves the issue. Triggering requires a vulnerable WebKit process to handle attacker-controlled content, and the confirmed consequence is a process crash rather than system shutdown or code execution.
Summary
What happened
Memory corruption in Apple WebKit before 26 allows remote attackers to crash a process by supplying maliciously crafted web content. Apple identifies WebKit Bugzilla 296490 but has not published the faulty function or memory operation, stating only that improved memory handling resolves the issue. Triggering requires a vulnerable WebKit process to handle attacker-controlled content, and the confirmed consequence is a process crash rather than system shutdown or code execution.
The record
- CVE
- CVE-2025-43343
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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 <26
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