Apple shipped iOS 26.6.1 and iPadOS 26.6.1 on 17 August 2026, alongside macOS Tahoe 26.6.2 and, the following day, Safari 26.6.1.
Start with the thing most coverage buries: Apple does not describe any of these issues as actively exploited. There is no "Apple is aware of a report that this issue may have been exploited" line in the advisory. That matters, because Apple does use that wording when it applies, and its absence is informative. This is an important update, not an emergency one.
The entry that matters
CVE-2026-65346 — ImageIO. Apple's own wording:
Impact: Processing an image may lead to arbitrary code execution
Description: An integer overflow was addressed with improved input validation.
Credited to Nik Tsytsarkin of Meta Red Team X.
Read the impact line carefully. Not opening a malicious app. Not visiting a website. Processing an image.
ImageIO is the framework that decodes image data across the operating system, and it runs in far more places than a photo viewer: message previews, notification thumbnails, AirDrop, mail rendering, the share sheet. A bug reachable through it is reachable by anything that can put an image in front of the device — which historically has meant no user interaction at all.
That is why ImageIO has an outsized track record. It is a large body of parsing code for dozens of complex formats, sitting behind entry points that fire before a person decides whether to trust the sender. A second ImageIO fix in the same release, CVE-2026-65347, is a denial-of-service via the same "processing an image" surface.
An integer overflow in a parser is the classic route to a heap write: a length or offset calculation wraps, an undersized buffer is allocated, and the copy that follows goes past its end.
Also worth flagging
CVE-2026-65329 — Telephony. An attacker in a privileged network position may bypass IPSec authentication, fixed by improved state management. Credited to Bedran Karakoc, Tobias Funke, Jacopo Clark and Katharina Kohls.
This got almost no coverage and probably should have. IPSec authentication is what protects carrier-side signalling paths; a state-management flaw there is a mobile-network attack, not an app-store one. The threat model is someone with position on the network — a rogue base station, a compromised carrier link — which is a smaller set of adversaries but a considerably more capable one.
Three kernel fixes. CVE-2026-65343 (use-after-free; a remote attacker may cause
unexpected system termination), CVE-2026-65349 (out-of-bounds read; may read kernel
memory), and CVE-2026-65330 (memory corruption).
Roughly twenty WebKit CVEs, the usual mix of memory corruption and unexpected Safari
crashes from maliciously crafted web content, plus CVE-2026-64778 in WebKit History
leaking sensitive data on visiting a crafted site.
CVE-2026-64788 — IOGPUFamily. Memory corruption from processing maliciously crafted web content, which is a browser-reachable path into a graphics driver.
What to do
Update. iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later.
For anyone in a plausible targeting category — journalists, executives, people who work on things governments care about — Lockdown Mode remains the meaningful control here. It restricts exactly the surfaces this update is patching: it blocks most message attachment types before ImageIO ever sees them, and disables complex web technologies that WebKit bugs depend on. It is a real trade in convenience, and for a small number of people it is a trade worth making.
Devices on the iOS 18 line got iOS 18.7.10 and iPadOS 18.7.10 the same day.
Source
Every impact and description quoted above is Apple's own wording from the iOS 26.6.1 advisory. Verify the CVE list against that page before republishing — Apple revises these advisories after publication.