Apple released iOS 27.2 and iPadOS 27.2 on October 26, 2026 with fixes for 163 security flaws. The most serious sit in WebKit, the engine behind Safari and most in-app browsers on iPhone and iPad. Eight of the WebKit and related entries are listed as arbitrary code execution from crafted web content, and two more let a remote attacker break out of the WebContent sandbox. Apple does not report any of them as exploited. Update anyway: the advisory is public, and a crafted page is all the worst bugs need.
This post is based on Cyber Security News' write-up of Apple's security content document for the release. We have not tested the bugs or read Apple's page line by line ourselves, so treat counts as the reporter's reading of the advisory and check Apple's security releases page for the authoritative list.
Quick answers
| Question | Answer |
|---|---|
| What shipped? | iOS 27.2 and iPadOS 27.2, plus iOS 26.7.2 and iPadOS 26.7.2 for devices still on 26. |
| How many fixes? | 163 security entries. |
| Worst bugs? | WebKit use-after-free and type confusion flaws that allow code execution from a crafted page. |
| Sandbox escapes? | Two: CVE-2026-113897 (WebKit Process Model) and CVE-2026-112690 (App Store). |
| Exploited in the wild? | None reported by Apple. |
| Who needs it? | Everyone on a supported iPhone or iPad. Organizations should treat it as a priority patch. |
The WebKit code-execution bugs
WebKit has the largest group of fixes, with more than 30 entries. Eight are described as arbitrary code execution when the device processes malicious web content:
| CVE | Component | Bug class |
|---|---|---|
| CVE-2026-112697, CVE-2026-112655, CVE-2026-112651, CVE-2026-112623 | WebKit | Use-after-free |
| CVE-2026-112659 | WebKit | Type confusion |
| CVE-2026-112637 | WebKit Canvas | Use-after-free |
| CVE-2026-112626 | WebKit JavaScript Bindings | Use-after-free |
| CVE-2026-112639 | WebKit Process Model | Use-after-free |
In a use-after-free, the browser keeps using memory after it has been released, so an attacker who controls what lands there can steer execution. Type confusion treats one kind of object as another with the same effect. Apple's stated fix for each is better memory management or state handling. Nothing is needed from the user beyond opening a page, which is why browser fixes on iPhone are treated as urgent.
Two sandbox escapes
Code running inside a browser is normally confined. A sandbox escape removes that confinement, so a WebKit bug becomes a route to the rest of the device.
- CVE-2026-113897, WebKit Process Model: a remote attacker may break out of the Web Content sandbox. Apple removed the vulnerable code.
- CVE-2026-112690, filed under App Store: the same impact, fixed with improved input validation. It was reported by Claudio Bozzato and Francesco Benvenuto of Cisco Talos.
Neither entry is listed as exploited, and they are separate from the code-execution entries above. Together they describe the shape of a chain: render a page, execute code, leave the sandbox. We are not saying anyone has built that chain here; the advisory does not say so.
Kernel, privacy and file-parsing fixes
About 15 kernel bugs are patched. Several are use-after-free flaws (CVE-2026-65350, CVE-2026-112679, CVE-2026-112517, CVE-2026-112514) that can crash the system or corrupt kernel memory. Others write kernel memory or reveal its layout (CVE-2026-112665), which helps an attacker plan a deeper break-in. Most need a malicious app or an existing foothold, so they matter mainly as the second step in a chain.
Privacy fixes are spread across everyday apps:
- Apple Intelligence, CVE-2026-86987: a remote attacker may access sensitive user data on iPhone 15 Pro and later and supported iPads.
- Mail, CVE-2026-112500: Hide My Email could leak the user's original address.
- CoreMedia, CVE-2026-86990: a malicious app could use the camera without permission.
- Maps, CVE-2026-112707: an app could see which other apps are installed.
- Further entries cover Contacts, Calendar, CloudKit, Files, Photos, Siri, Shortcuts and Screen Time.
Parsers for images, PDFs, fonts, audio and 3D models (ImageIO, CoreGraphics, CoreAudio, FontParser, Model I/O) received many fixes. Most crash an app or leak process memory. CVE-2026-112688 in CoreMedia can lead to code execution when a file is parsed. One oddity in the list: Spotlight includes CVE-2022-26704, an older symlink validation fix, alongside the 2026 numbers.
AI-found bugs and the jailbreak connection
Credits in the WebKit entries include a researcher at OpenAI Codex Security, Chris Rohlf with Anthropic Research, and several independent researchers. AI-assisted bug hunting is now a normal source of vendor advisories, which is the dynamic we looked at in OpenAI's Patch the Planet framework and Trail of Bits' regression hunt. Expect advisories this size to become more common, and patch windows to matter more.
Six entries credit the Calif team, which demonstrated a jailbreak on iOS 27.0.1. Calif researcher Stefan Esser has said most of the bugs used for it are fixed in 27.2. Public research tends to follow a jailbreak demo, which is another reason not to sit on a large point release.
What to do
- Update. Open Settings, tap General, then Software Update. Back up first.
- Pick the right build. iOS 27.2 or iPadOS 27.2 on the current branch, or 26.7.2 if the device is still on iOS 26. Do not skip the update because you are not on the newest major version.
- Check eligibility. Supported hardware starts at iPhone 11 and includes iPad Pro 12.9-inch 4th generation, iPad Pro 11-inch 2nd generation, iPad Air 4th generation, iPad 9th generation and iPad mini 6th generation.
- For teams, pull a device inventory and confirm the OS version of every managed phone and tablet within days, not weeks. Your MDM tool is the place for that; see Beam MDM for Apple and Windows devices for how Beam handles enrollment and inventory.
- Treat links with care until you are patched, especially links from unfamiliar senders and pages opened in in-app browsers.
Why developers who run AI agents should care
The phone is part of the agent workflow even when no agent runs on it. It holds the authenticator that approves a sign-in, receives the alert that a deploy or key rotation is needed, and opens the links agents print into chat and pull requests. Our write-ups of a Claude session bridge claim with a Chromium patch gap and of the WebGPU browser risk for agents show how much of the attack surface is simply a browser that is behind on patches. A phone taken over through WebKit undermines the approval steps you rely on.
For the broader patch discipline, see what to do after an attack on your app, the Oracle Java October 2026 CPU and the October 2026 attacks timeline.
What Beam can and cannot do here
Beam runs on a developer machine and watches what coding agents such as Claude Code and Codex do, flags risky actions, and scans skills and MCP configurations with heuristics. It does not install iOS updates, inspect iPhones or iPads, or detect WebKit exploitation. The control for this advisory is the OS update itself.
Related reading
- OpenAI's Patch the Planet framework
- Oracle Java SE October 2026 CPU
- Beam MDM: Apple and Windows device management
- WebGPU and AI agent browser risk
- Microsoft October 2026 Patch Tuesday: 1,411 flaws and one exploited Windows Shell zero-day
Primary sources: Apple security releases · Cyber Security News coverage
Accurate as of October 28, 2026. Counts and descriptions come from press coverage of Apple's advisory; check Apple's security content page for the current list.