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 memory corruption.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.4",
  "pubDate": "2026-08-17T22:17:25.103Z",
  "pubdate": "2026-08-17T22:17:25.103Z",
  "executiveSummary": "This vulnerability involves a memory corruption flaw resulting from improper memory handling within the processing pipeline for web content across multiple Apple operating systems. Successful exploitation of this issue can lead to arbitrary memory corruption, potentially allowing an attacker to achieve arbitrary code execution or cause an application crash.\nThe affected products include iOS and iPadOS versions prior to 18.7.10 and 26.6.1, alongside macOS Tahoe versions prior to 26.6.2. The risk implications are severe due to the potential for remote code execution via compromised or maliciously crafted web content.\nAttacker capabilities require the delivery of malicious web content to the targeted victim, typically necessitating user interaction such as enticing the user to visit a compromised website or view hostile web resources within vulnerable browser components or applications rendering web content.",
  "technicalDetails": "The vulnerability stems from improper memory handling within the component responsible for processing web content. Specifically, flaws in memory allocation, management, or deallocation routines allow an adversary to supply maliciously crafted web inputs that trigger memory corruption states, such as buffer overflows, use-after-free conditions, or out-of-bounds reads and writes.\nThe attack flow initiates when a victim processes maliciously crafted web content via the vulnerable web rendering engine. The input data exploits the flawed memory handling logic during parsing or rendering operations. As the engine handles the malformed structures, memory safety violations occur, leading to corrupted internal state representations.\nNetwork exposure is inherent to processing web content, making remote exploitation feasible if a user navigates to an attacker-controlled web page or interacts with embedded malicious web payloads. Authentication and specific privilege requirements are generally not required to trigger the initial parsing vulnerability, as it manifests upon processing untrusted external inputs.\nThe post-exploitation impact includes the potential overwrite of critical data structures in memory, leading to application instability or the execution of arbitrary code within the context of the running process. Depending on the privilege boundaries of the affected component, this may facilitate sandbox escapes or further system compromise."
}