Description

The issue was addressed with improved memory handling. This issue is fixed in iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2. Processing maliciously crafted web content may lead to an unexpected Safari crash.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.3",
  "pubDate": "2026-08-17T22:17:24.747Z",
  "pubdate": "2026-08-17T22:17:24.747Z",
  "executiveSummary": "This vulnerability involves a memory handling flaw within the Safari web processing components of affected Apple operating systems.\nThe primary impact of this issue is an unexpected application crash resulting from the processing of maliciously crafted web content.\nThe affected systems and products include iOS 18.7.10, iPadOS 18.7.10, iOS 26.6.1, iPadOS 26.6.1, and macOS Tahoe 26.6.2.\nThe risk implications are primarily associated with denial of service conditions affecting the Safari browser application during the parsing of hostile web resources.\nAttacker capabilities require the ability to deliver or host maliciously crafted web content to the targeted user, typically via a compromised website or a crafted hyperlink.\nExploitation requirements dictate that the victim must process the hostile web content using an unpatched instance of the vulnerable Safari browser environment.",
  "technicalDetails": "The root cause of the vulnerability stems from improper memory handling within the web content processing engine of Safari.\nThe vulnerable component is responsible for parsing and rendering web content, where memory allocations and deallocations fail to manage specific edge cases securely.\nExploitation occurs when an attacker induces a target user to process maliciously crafted web content, such as a specially designed webpage containing malicious markup, scripts, or embedded media.\nThe attack flow begins as the victim navigates to a malicious URL or interacts with hostile web content rendered by the browser.\nUpon encountering the malformed structures within the web content, the vulnerable memory handling routines trigger an anomalous state.\nThis anomalous state results in an immediate and unexpected crash of the Safari application, denying service to the user and disrupting active browsing sessions.\nNetwork exposure is present externally through normal web browsing activities, as the vulnerability is triggered via remote web content.\nAuthentication and privilege requirements are minimal for the attacker, as the vector relies solely on the victim's interaction with standard web traffic.\nPayload behavior is confined to causing an application termination or denial of service, with no explicit remote code execution capabilities detailed in the baseline description."
}