Apple Safari CVE-2026-65337

Exploitation requires that the victim actively navigate to or load attacker-controlled web content in an unpatched Safari browser (UI:R); passive network interception alone is insufficient. The vulnerability is triggered during web content processing, so the standard Safari browsing configuration is the only prerequisite - no special Safari feature, non-default setting, or server-side component needs to be enabled. Exploitation is limited strictly to causing a Safari application crash (A:L); no privilege escalation, code execution, or data exfiltration is achievable via this vulnerability alone. The requirement for user interaction (clicking a link or being redirected) meaningfully limits scalability of attacks compared to zero-click vectors.

The CVSS 3.1 base score of 4.3 (Medium) reflects the constrained impact profile: AV:N (network-reachable attack surface via the browser), AC:L (low complexity to trigger), PR:N (no authentication required of the attacker), but critically UI:R (victim must navigate to attacker-controlled or injected content) and scope unchanged with only A:L (partial availability - application crash, not system crash). The impact is exclusively a DoS crash; C:N and I:N confirm no confidentiality or integrity risk. EPSS at 0.14% (4th percentile) aligns with the DoS-only nature and the requirement for user interaction - mass exploitation is unlikely. No CISA KEV listing and no public exploit code further corroborate low near-term exploitation probability. This is a real but low-priority issue for most organizations: the primary risk is to consumer users or targeted individuals lured to a malicious page, not to enterprise infrastructure. Security teams should prioritize the patch as part of routine Apple OS update cycles rather than emergency response.

An attacker crafts a malicious webpage containing specially structured web content (likely malformed HTML, CSS, or JavaScript) designed to induce an inconsistent state in WebKit's rendering engine. The attacker distributes the URL via phishing, social engineering, or a malicious advertisement network, causing victim devices to open the page in Safari. Upon rendering, Safari crashes abruptly, disrupting the user's browsing session - repeatable if the user revisits the URL, creating a persistent denial-of-service condition for targeted individuals. No code execution is achieved, and no public proof-of-concept exists at this time.