Apple iOS/iPadOS CVE-2026-86886

Requires a locally-installed, attacker-controlled app already executing on the device (PR:L, AV:L, UI:N); it then abuses a file-handling path that fails to validate traversal sequences to write to protected system-file locations. Exploitation is limited to unpatched iOS/iPadOS before 26.7/27 and watchOS before 27, and is bounded by Apple's app-distribution and code-signing controls that make delivering and running a malicious app the primary hurdle. Impact is confined to unauthorized modification of protected files (integrity); no data disclosure or denial-of-service is claimed. This is not remotely exploitable and requires no additional configuration once malicious code runs.

Signals are consistent and point to a moderate, gated local vulnerability rather than an urgent priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, base 5.5) describes a locally-installed, low-privileged malicious app that gains a high-integrity write primitive against protected system files (no confidentiality or availability impact). EPSS is very low at 0.16% (6th percentile), consistent with the absence of any public exploit or CISA KEV listing and the fact that exploitation requires already running attacker-controlled code on the device. There are no conflicting signals: the local attack vector, low-privilege gate, and integrity-only impact all align, and Apple self-reported the flaw. Under an SSVC lens this is not automatable (requires app installation/execution on a target device), technical impact is partial (integrity write of protected files, no code-exec or data-read claimed), and exploitation is 'none' observed - placing it in a low-priority/track band. Net: a real defense-in-depth sandbox-escape-adjacent issue worth patching in normal cycles, but not a widespread-exploitation emergency.

An attacker publishes or sideloads a malicious app to a victim's iPhone, iPad, or Apple Watch. Once running in its sandbox, the app supplies crafted path components that, due to insufficient input validation, traverse outside its permitted directory to write or alter protected system files it should not be able to touch. No public exploit code is identified, and the local, low-privilege attack vector means the attacker must first get code executing on the device.