Apple iOS EUVD-2026-78117

Exploitation requires three concrete things: a malicious or compromised application installed on the target device, the ability to execute that app so it reaches the affected kernel interface, and user interaction to launch it (CVSS UI:R) - there is no network-reachable vector (AV:L). The description gives no "when configured with..." qualifier, so no non-default setting or special entitlement is documented as a prerequisite. What limits impact: the flaw is confined to confidentiality (C:H/I:N/A:N), so no code execution, privilege escalation, or denial of service results directly; it is platform-specific to the listed Apple OS versions prior to the fixed releases; and the app must remain running long enough to trigger the vulnerable path. It cannot be exploited remotely and does not affect users who never install or launch untrusted apps.

Signals point to a low-priority, defense-in-depth fix rather than an emergency patch. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N = 5.5) makes clear this is neither remotely reachable nor unauthenticated in the network sense: the attacker must already have a locally executing app and must convince the user to launch it, and Apple explicitly assigns no integrity or availability impact. EPSS is only 0.21% (11th percentile), squarely micro-targeted, and there is no KEV listing and no reported POC - exploit status is "no public exploit identified at time of analysis." Note that the base score is driven almost entirely by C:H; if chained with a separate kernel memory-corruption bug it becomes far more valuable, so it is a chaining primitive rather than a standalone threat. Data caveats: the input provides only "Patch: Available from vendor" without granular per-OS release dates, the reference titles are empty (cveorg entries carry no labels), and the EUVD affected-version ranges use the generic "0 <X" form, so exact earlier affected point releases cannot be enumerated from the supplied data.

An attacker distributes a malicious or trojanized app through a sideloading channel, enterprise certificate, or social-engineering lure, and the victim launches it. On execution the app triggers the affected kernel code path and reads back uninitialized memory, harvesting kernel pointers that reveal the layout of kernel memory and defeat KASLR. The attacker then combines that layout knowledge with a separate kernel memory-corruption exploit to achieve reliable privilege escalation - this CVE alone yields no code execution.