Browser crash via type-confused state handling
Published May 12, 2025 · Updated Apr 2, 2026
Type confusion in WebKit across Apple products before the listed May 2025 releases allows remote attackers to crash Safari with crafted web content. Apple identifies improper WebKit state handling but has not disclosed the confused types, code path, or state transition that misclassifies data. A user must process attacker-controlled web content, and the documented consequence is an unexpected Safari crash rather than system compromise.
Summary
What happened
Type confusion in WebKit across Apple products before the listed May 2025 releases allows remote attackers to crash Safari with crafted web content. Apple identifies improper WebKit state handling but has not disclosed the confused types, code path, or state transition that misclassifies data. A user must process attacker-controlled web content, and the documented consequence is an unexpected Safari crash rather than system compromise.
The record
- CVE
- CVE-2025-31206
- Published
- May 12, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-843, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2025CVE publishedPublication date reported by the CVE source.
- Apr 2, 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.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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