A newly published proof-of-concept exploit has put several older Apple devices back in the spotlight, especially the iPhone XS through the iPhone 11 lineup. The issue reaches the BootROM layer, the earliest code that runs before iOS starts loading, which makes it far more serious than an ordinary software bug.
Because BootROM is permanently embedded in the chip during manufacturing, Apple cannot fully remove this weakness through an iOS update. That means devices affected by the flaw are expected to keep the vulnerability at the hardware level.
Why the flaw matters
The exploit, known as usbliter8, was published by European cybersecurity research firm Paradigm Shift. It targets a defect in the USB controller integrated into Apple’s A12 and A13 chips, which are used across the iPhone XS, iPhone XR, and the iPhone 11 series, along with certain iPads and older Apple Watch models using related silicon.
According to the researchers, the attack works during startup, when the USB controller normally stores incoming data in memory buffers. By sending a carefully timed stream of very small USB packets during boot, the exploit can manipulate how that buffer is handled.
Attack flow at the earliest boot stage
The researchers say the flaw can cause low-level memory corruption and force an internal pointer in the USB controller to move backward instead of forward. That can open the door to writing data into memory areas that should normally remain protected.
On A12-based devices, the reported result is relatively direct control over the processor. Once triggered, the exploit can weaken some security restrictions and run unsigned software that would ordinarily fail Apple’s verification checks.
A13 devices are described as more complicated because Apple added Pointer Authentication Codes, or PAC, a hardware security feature designed to detect unauthorized memory changes. As a result, bypassing A13 protection requires a staged exploit before code execution can happen.
Devices included in the affected range
The models specifically named as affected include the iPhone XS, iPhone XS Max, iPhone XR, iPhone 11, iPhone 11 Pro, and iPhone 11 Pro Max. Several A12-, A12X-, A12Z-, and A13-based iPads are also said to be vulnerable, although the published proof-of-concept focuses on A12 and A13 devices.
Paradigm Shift also confirmed support for Apple’s S4 and S5 chips, which are used in older Apple Watch models. The scope therefore extends beyond iPhone alone, even though the main concern remains the iPhone models powered by A12 and A13.
| Chip or device group | Status |
|---|---|
| A12 and A13 devices | Targeted by the usbliter8 proof-of-concept |
| iPhone XS and iPhone 11 family | Specifically named as affected |
| iPhone X with A11 | Not affected |
| A14 and later | Protected by newer BootROM memory safeguards |
Not every nearby generation is exposed to the same weakness. The iPhone X with the A11 chip is said to be unaffected because Apple added an extra USB pointer reset mechanism in BootROM.
Devices with A14 and newer chips are also reported to remain protected. The researchers say Apple enabled the correct memory protection mechanism at the BootROM level on those later devices.
What users should understand
Even so, the exploit has an important limitation: it requires physical access to the device. That makes it different from remote attacks that can be launched through the internet or a malicious message.
The researchers also say Secure Enclave is not affected. That separate security component handles certain sensitive data, so usbliter8 does not automatically break every part of Apple’s device security.
The exploit is not a full jailbreak either. What has been published so far is a proof-of-concept, meaning a technical demonstration that shows the flaw is real and can be used under certain conditions.
Paradigm Shift said it reported the issue to Apple before publication and used coordinated disclosure. Even with those steps, the public release of the code has increased concern because the technical details are now available for wider scrutiny.
Since the flaw sits in USB controller hardware and reaches the BootROM layer, iOS updates are not viewed as a fix for the root cause. For users of affected devices, moving to newer hardware is described as the most effective way to leave the issue behind.