Apple's Newest Unpatchable Exploit Hits iPhone XR to iPhone 11 — Permanently

Apple
Sunday, 21 June 2026 at 11:52
image_1782036187728
Add as a preferred source on Google
Paradigm Shift, a security research firm, published a working proof-of-concept exploit on June 18 called usbliter8. It achieves arbitrary code execution inside the SecureROM of Apple's A12 and A13 chips — the immutable boot code physically burned into the silicon at manufacture. No software update can reach it. No iOS patch will ever fix it. Every affected device is permanently compromised at the hardware root of trust for the rest of its operational life.
a13_bionic_mockup_1782036061112

Summary

  • usbliter8 exploits a hardware flaw in the Synopsys DWC2 USB controller combined with a DART bypass mode in SecureROM on A12, A13, S4, and S5 chips — covering iPhone XR through iPhone 11 series, multiple iPads, three Apple Watch models, and more.
  • The attack requires physical access, a USB cable, and the device in DFU mode — it completes in under two seconds and leaves a "PWND" marker in the device's USB serial number.
  • The Secure Enclave is not directly breached — passcodes and encrypted data remain protected — but Paradigm Shift warns the compromise opens broader indirect attack paths toward the SEP.
  • No CVE, no CVSS score, no Apple security advisory, and no in-the-wild exploitation have been reported as of June 19, 2026.
  • A14 and newer chips configure DART correctly, making them immune; A11 and older are unaffected by a separate design path — only A12 and A13 families are in scope.

The Closest Comparison Is checkm8 — And That Should Tell You Something

The last publicly known BootROM exploit of this kind was checkm8, released in 2019, which affected devices from the iPhone 4S through to the iPhone X. usbliter8 now extends that history to the next generation of chips, covering the iPhone XS through to the iPhone 11 series.
image_1782036191996
That's not a comfortable precedent. checkm8 has been in active use by jailbreak communities, forensics firms, and law enforcement tools for seven years. usbliter8 begins the same clock for A12 and A13 hardware — and there are tens of millions of these devices still in daily use worldwide.
The exploit chains a hardware-level bug in the Synopsys DWC2 USB controller with a firmware configuration flaw, enabling full application processor boot-chain compromise with no software patch possible due to the immutable nature of BootROM code.
On A12 devices the attack is relatively straightforward — the DMA buffer sits adjacent to the USB task's stack on the heap, allowing a saved link register to be corrupted and program counter control handed to the attacker. A13 is harder; Pointer Authentication (PAC) protects return addresses, so Paradigm Shift bypassed it through heap corruption and panic depth counter manipulation. Either way, execution completes in under two seconds.
"Paradigm Shift's usbliter8 is usbliter8's checkm8 moment — a permanent, unpatchable BootROM exploit that will define the security posture of hundreds of millions of Apple devices for as long as they stay in use."

What's Actually at Risk — and What Isn't

The Secure Enclave is a different matter. usbliter8 does not directly breach it, which means passcodes and encrypted user data remain protected. A BootROM-level compromise is not an instant data dump. Paradigm Shift does note, though, that a compromise of this depth could open broader attack paths toward the Secure Enclave even without breaching it directly.
The real-world risk profile depends heavily on context. For most consumers, the barrier to exploitation is meaningful: an attacker needs physical possession of the device, a USB connection, manual entry into DFU mode, and technical knowledge to execute the chain.
A device sitting in a pocket, unpowered or in normal use, is not spontaneously compromised by this disclosure.
Strong passcodes and physical custody of your device still matter.

Who Should Actually Worry

For high-security environments, this is now a hardware-retirement and device-custody problem.
If you're running A12 or A13 devices in enterprise, government, legal, medical, or any role where device integrity is a compliance requirement, the guidance is clear: audit A12, A13, S4, and S5 hardware in sensitive roles and prioritize refreshes toward A14 or newer.
A12X and A12Z chips — found in 2018 and 2019 iPad Pro models — could also have technical support for this issue, though implementation hasn't been confirmed, so those devices may also be in scope.
No CVE has been assigned and Apple has issued no formal advisory as of June 19.
No in-the-wild exploitation has been publicly reported.
As word spreads, the jailbreak community will move quickly — usbliter8 is already generating significant interest in those circles for exactly the same reasons it concerns security teams.
loading

Loading