Calif.io's iPhone 18 Pro jailbreak regained root after a reboot on stage at Hexacon

We would expect Apple to patch this, since Decrypt reports that Apple usually patches such chains once it learns the details ^[14]. The order of events is the open part. Apple could fix the chain before Calif publishes, if it already holds the details. Calif could publish first, with Apple following. Or the published chain could turn out to need the phone in hand, as a demo that ends in a passcode unlock might ^[5], and the exposed group would shrink.

The only public link between Calif.io and Apple's patch process is the credit in the September 14 security notes, which are 32 days older than the demo ^[12]. Decrypt reports that nothing in those notes ties either credited bug to the jailbreak ^[7].

Persistence is what gives the demo weight. Decrypt says getting root on a current iPhone usually means chaining a sandbox escape, a kernel compromise and a bypass of hardware-backed protections like Pointer Authentication Codes, and that persistence across a reboot is tougher again, since Apple verifies code at startup ^[9]. In our view that justifies a weaker assumption about device trust for the small set of users worth a targeted attack, and no change for the rest of a fleet today. We would be wrong about the size of that set if the published chain needs no physical access, and a stage video cannot show that either way.

The cost side is open. Decrypt reports no build time for the iPhone chain. The nearest comparison is May's macOS kernel exploit against Apple's M5 chip protections, which Calif said it built in under a week with help from Anthropic's Claude Mythos Preview ^[11]. If the iPhone chain cost anything like that, a patch closes one chain and the next demo follows on a short schedule. That rests on one firm's account of its own work.