Unpatchable “usbliter8” Exploit Breaks Apple’s A12 and A13 SecureROM

Unpatchable “usbliter8” Exploit Breaks Apple’s A12 and A13 SecureROM

Security researchers have disclosed a new vulnerability that strikes at the deepest layer of Apple’s boot process, and unlike most software flaws, this one cannot be fixed with an update. The exploit, named usbliter8, was published on June 18, 2026 by the security research firm Paradigm Shift, and it affects every device built around Apple’s A12 and A13 chips.

That list covers a wide range of hardware still in daily use today, including the iPhone XS, XS Max, and XR, the iPhone 11 lineup and iPhone SE (2nd generation), several iPad models, and Apple Watch units running the S4 and S5 chips. The HomePod mini and the second-generation Apple TV 4K also share the vulnerable silicon.

Why It Can’t Be Patched

The flaw lives inside SecureROM, the very first piece of code that runs the moment a device powers on. This code is permanently etched into the chip during manufacturing, which means there is no firmware update path that can ever reach it. Any device successfully exploited remains in that state for its entire operational life, surviving iOS updates, restores, and factory resets.

Paradigm Shift traced the root cause to a hardware bug in the Synopsys DesignWare USB controller used in these chips. During Device Firmware Update (DFU) mode, the controller’s memory protection is left in a bypass state, allowing carefully crafted USB packets to corrupt memory and ultimately hand an attacker control over the boot process before iOS ever loads.

A12 vs. A13: Two Different Challenges

Getting code execution wasn’t equally easy across the two chip generations. On the A12, the exploit path is relatively direct, since a key memory buffer sits close to a USB task’s stack in memory. On the A13, Apple’s Pointer Authentication Codes (PAC) stood in the way, designed specifically to catch this kind of memory tampering. Researchers got around it through a multi-stage process: corrupting heap structures to gain limited write access, manipulating an error counter to stop the chip from rebooting mid-attack, and finally overwriting a USB interrupt handler to gain full control.

Echoes of Checkm8

The closest comparison is checkm8, the SecureROM exploit released in 2019 that permanently affected every Apple device from the A5 through the A11 chip. Like checkm8, usbliter8 has already become a foundation people expect the jailbreaking community to build on, since both share the same physical-access, DFU-mode requirements and the same permanent, hardware-level reach.

Apple’s newer chips are not affected. Starting with the A14, the company configured the same USB memory protection correctly from the outset, closing off this particular path. That leaves A12 and A13 devices sitting in a gap: too new to have had the A11-era workaround, and released just before Apple corrected the configuration going forward.

What This Doesn’t Touch

There is an important limit to what usbliter8 can do. It does not break into the Secure Enclave, the separate, isolated chip responsible for protecting passcodes and encrypted user data. Researchers noted, however, that boot-level control of this depth could potentially open new avenues for attacking the Secure Enclave indirectly, though no such attack has been demonstrated publicly.

Paradigm Shift coordinated its disclosure with Apple’s security team ahead of publication and released a working proof-of-concept alongside its technical write-up. As of this week, Apple has not issued a security advisory or CVE for the issue, and there are no public reports of the exploit being used maliciously in the wild.

For most users, the practical risk remains low, since exploitation demands physical access to an unlocked or DFU-mode device along with specialized hardware. Owners of affected devices who are concerned about physical security should be aware that, unlike a typical software bug, this one has no patch on the horizon — the only way to fully avoid it is moving to newer hardware.