iPhone 18 Pro Jailbreak: What Calif’s Demo Shows
Calif demonstrated an untethered jailbreak on an iPhone 18 Pro. See what the reboot test proves, what remains unknown, and what iPhone users should do next.

An iPhone 18 Pro Jailbreak Survived a Reboot. Here's What That Means
A jailbreak demo is easy to misread. It can sound like a new tool is ready for anyone to install, or that every iPhone on the same software is now compromised. Calif's demonstration at Hexacon in Paris points to something narrower - and technically important: researchers showed root access on an iPhone 18 Pro running iOS 27.0.1, then rebooted the phone and showed that the access returned without using a computer.
That's the core takeaway. An "untethered" jailbreak is designed to survive a restart, not just keep working for one session. Still, Calif hasn't named the vulnerabilities it used, released a jailbreak tool, or said when it plans to publish technical details. Apple also hasn't commented publicly on the stage demo. So the practical risk for everyday users isn't clear yet.
This article separates what the demo showed from what remains unknown. It also looks at how untethered jailbreaks differ from other exploit setups, why reboot persistence matters, what Apple's published security notes do and don't tell us, and what iPhone owners can do while the details are still private.
What Calif demonstrated at Hexacon
At Hexacon, an offensive security conference in Paris, security firm Calif demonstrated an untethered jailbreak on an iPhone 18 Pro running iOS 27.0.1. The presentation took place on October 16, 2026, the opening day of the two-day event.
Video posted by jailbreak researcher Billy Ellis shows the team restarting the phone, unlocking it with the regular passcode, and starting an SSH session as root. Root is the highest level of access on the device. The on-screen terminal output identified iOS 27.0.1 and showed an uptime of about two minutes.
The sequence matters: jailbreak, reboot, then root access again. A jailbreak that works only until the next restart is different from one that still works after the phone boots normally. Calif described its demo as untethered, meaning they didn't need a computer to reapply the jailbreak after rebooting.
What a jailbreak changes
Apple limits what software can do on an iPhone using operating-system and hardware protections. Apps typically run in sandboxes, and the device checks parts of the software chain during startup. Together, these controls reduce how much any single app can do and make it harder to run code Apple hasn't authorized.
A jailbreak bypasses some of those restrictions and can give the operator root access. Depending on the method and what tools are available, that can enable things like installing software outside Apple's App Store, changing system behavior, or accessing parts of the file system that are normally off-limits.
None of that means every jailbreak offers the same capabilities, is simple to use, or makes sense for everyday users. "Jailbreak" is a broad label for a category of techniques, not one single feature set. Calif hasn't released a public tool or described the full capabilities of the jailbreak shown at Hexacon.
A demonstration is not a consumer release
This distinction is important. The stage video is evidence that Calif demonstrated a working exploit chain in a controlled setting. It's not an installation guide, a public jailbreak package, or proof that a typical attacker can compromise every iPhone 18 Pro remotely.
Calif's conference newsletter listed several demonstrations, including an iMessage demo and a one-click Signal demo, and said the work would be released "in due time." That phrase doesn't tell you a release date, or whether Calif plans to publish source code, a technical write-up, or a usable tool.
For now, the publicly available evidence is limited to the demo and Calif's statements. The vulnerabilities involved, what the jailbreak requires, how reliable it is, and what real attack scenarios might look like are still undisclosed. Readers should treat anything beyond those facts as unconfirmed.
Why surviving a reboot matters
"Untethered" means the jailbreak can persist across a restart. It does not mean the vulnerability is permanent, that Apple can't patch it, or that the jailbreak will survive every future iOS update. Those are separate questions.
Many exploit demos provide access only for the current session. After a reboot, the altered state can disappear, forcing the operator to reconnect the device to a computer or repeat steps before regaining access. An untethered jailbreak is tougher because the modified state comes back after a normal restart - without external intervention.
The security chain behind root access
On a modern iPhone, getting root access usually isn't about finding one bug and taking over the device right away. An exploit chain may need to cross multiple security boundaries. In general terms, that can involve escaping an app's sandbox, gaining control at the kernel level, and working around hardware-backed protections.
Apple's Pointer Authentication Codes (PAC) are one example of hardware-backed defense. They help detect certain types of tampering with memory pointers. Defeating protections like that can make exploit development more difficult - but Calif's exact approach hasn't been disclosed. It would be guesswork to claim the demo relied on any specific vulnerability or bypass.
Reboot persistence adds another layer. During startup, the device checks important parts of the software chain. A technique that works while the phone is already running doesn't automatically explain why access returns after the device starts again. The stage demo shows the outcome, but not the underlying mechanism.
"Permanent" is not the same as unpatchable
Some coverage calls the demo a permanent jailbreak. In this context, the practical point is simply that root access came back after a reboot. That's not the same thing as a permanent weakness across every device, and it's not a guarantee that the same exploit will still work after Apple changes iOS.
A software update can close one or more vulnerabilities in an exploit chain. A jailbreak may also depend on a specific iOS build, device configuration, or a particular set of conditions. Until Calif publishes details, it's not possible to say which devices or versions are affected beyond the iPhone 18 Pro running iOS 27.0.1 shown in the demo.
That's why precise reporting matters. "Jailbreak survives a reboot" describes observed behavior. "All current iPhones are permanently vulnerable" doesn't match the evidence that's available.
What the demo means for iPhone security
The demo is a reminder that strong platform security isn't the same as invulnerability. Apple's layered protections raise the cost of an attack, but they don't prove that no exploit chain can exist. A successful demonstration on current hardware is relevant to researchers and defenders even when there's no consumer tool to install.
At the same time, a jailbreak demo doesn't automatically translate into a real-world attack against ordinary users. Reproducing it depends on the conditions behind the exploit. If a technique requires physical access, a specific software build, or a long sequence of steps, it's very different from a remote exploit that can be triggered through a message or a webpage. Calif hasn't disclosed what those requirements are for this jailbreak.
The connection to security research and spyware
Root access on a fully updated phone is valuable. Commercial spyware operators and other advanced attackers may look for comparable capability because it enables deeper control of a device. But a research demonstration doesn't prove that a spyware vendor has the same exploit, that the technique is being used in the wild, or that the public is dealing with an active campaign.
The gap between a proof of concept and an operational attack is real. Researchers often have to build a chain from multiple bugs, make it reliable across devices, and develop a delivery method. Those steps take time and can impose constraints. Without Calif's technical details, the demo should be treated as a serious research result - not as evidence of widespread compromise.
What Apple's security notes tell us
Apple's iOS 27 security notes, published September 14, credit Calif.io and collaborators working with Claude and Anthropic Research for two unrelated bugs that could allow an app to cause a denial of service or a system crash. Those notes don't connect either bug to the iPhone jailbreak shown at Hexacon.
It's easy to mix these stories up since the same names appear. Acknowledgment in a security bulletin confirms Apple credited researchers for specific reported issues. It doesn't reveal which vulnerabilities were used in a separate jailbreak demo unless Apple or Calif explicitly makes that connection.
Apple hasn't publicly commented on the stage demo. The company's general approach is to avoid confirming security issues until an investigation is complete and patches are available. Until there's an advisory or disclosure, the relationship between Calif's jailbreak and any publicly listed iOS 27 vulnerabilities remains unknown.
The role of AI in the wider research context
Calif has discussed using Anthropic's Claude models in security research. In April, Calif's Thai Duong wrote about using Claude to examine an iOS Safari exploit. In May, the firm said Claude Mythos Preview helped it develop a macOS kernel exploit involving Apple's M5 chip protections in under a week.
That history is useful context, but it doesn't prove that AI helped create the iPhone 18 Pro jailbreak. Calif hasn't said the jailbreak depended on Claude or Anthropic Research. Apple crediting Calif for two crash-related bugs also doesn't connect those bugs to the Hexacon demonstration.
The practical lesson is simpler: AI tools can support parts of vulnerability research, but the end result still depends on verification, exploit engineering, and a solid understanding of the target system. For this specific demonstration, the role of AI hasn't been disclosed.
What users should do while details are unknown
There's no public jailbreak tool to install, and the available information isn't enough to judge how likely a real-world attack is. For most iPhone users, the sensible move is normal security hygiene - no panic and no attempt to reproduce the exploit based on unverified instructions.
A reasonable approach looks like this:
- Install iOS updates when Apple releases them. Security updates are the main way known software vulnerabilities get fixed. If you can, keep automatic updates enabled.
- Be skeptical of claims that a "public jailbreak" is available. Calif hasn't released one. Random downloads that claim to be the Hexacon jailbreak are likely scams or may install unwanted software.
- Watch out for unexpected links and attachments. The exact attack requirements aren't known here. Until the details are clearer, avoiding untrusted content is a good baseline.
- Use a strong passcode and protect access to your device. The stage demo used the regular passcode to unlock the phone after reboot. That alone doesn't show the passcode was bypassed.
- Follow Apple's security advisories and any disclosures from Calif. A patch or technical report will tell you more than speculation about which bug was used.
If you manage devices in an organization, don't base incident-response decisions on a conference clip. Track the relevant Apple advisories, confirm which iOS versions your fleet runs, and stick to your normal patch-management process. If Calif publishes technical indicators - or if Apple issues guidance - update your assessment based on those new facts.
The bottom line is straightforward: don't dismiss the result, but don't blow it out of proportion. A demonstrated jailbreak is a big research milestone. But without a published exploit chain or evidence of real active exploitation, it's not enough on its own to justify emergency action for every user.
Conclusion
Calif's Hexacon demonstration showed an iPhone 18 Pro running iOS 27.0.1 returning to root access after a reboot. That matters because reboot persistence is harder than access that disappears when a device restarts. Still, it isn't a public jailbreak release, and it isn't proof that every current iPhone is exposed.
Key details remain undisclosed: which vulnerabilities were used, what conditions are required, whether the technique works beyond the demonstrated device and build, and when Calif will publish further information. Apple hasn't connected its published crash bugs to the exploit, and it hasn't publicly commented on the demo.
For now, keep devices updated and rely on confirmed advisories rather than speculation. We'll have a clearer security picture when Calif publishes the technical details or Apple issues guidance.