\n11-inch iPad Pro (1st generation)
\n11-inch iPad Pro (2nd generation)
\n12.9-inch iPad Pro (3rd generation)
\n12.9-inch iPad Pro (4th generation)
\nApple Watch Series 4
\nApple Watch Series 5
\niPad (8th generation)
\niPad Air (3rd generation)
\niPad mini (5th generation)
\niPhone 11
\niPhone 11 Pro
\niPhone 11 Pro Max
\niPhone SE (2nd generation)
\niPhone XR
\niPhone XS
\niPhone XS Max
<\/p>\n
Usbliter8 combines a hardware flaw in a USB controller with the way security protections are configured on affected devices. The attack works through Device Firmware Update mode, better known as DFU mode. <\/p>\n
Successful exploitation gives researchers control before iOS<\/a> even starts loading. The exploit also enables boot-chain compromise and custom USB request handling.
<\/p>\n The exploit can boot modified iPhone software that wouldn’t normally be allowed to run. Paradigm Shift’s reporting is serious because the vulnerability exists in SecureROM, the first code that runs when an iPhone starts up.
<\/p>\n SecureROM verifies Apple’s software before the rest of the operating system loads and serves as the foundation of the device’s security model. Apple can patch flaws in iOS, iPadOS<\/a>, and watchOS<\/a> through software updates.
<\/p>\n The code is built into the chip itself and can’t be replaced after manufacturing. Affected devices will remain vulnerable unless users replace them with newer hardware.
<\/p>\n Usbliter8 doesn’t affect A14 chips or newer generations because later versions of SecureROM appear to configure hardware protections differently. A11-based devices also avoided the vulnerability because their USB driver resets memory addresses in a way that prevents the attack.
<\/p>\n Why the exploit matters<\/p>\n Apple’s security architecture checks each stage of the startup process before handing control to the next one. A successful SecureROM exploit can bypass some of those checks and gain access at the earliest stage of device startup.
<\/p>\n SecureROM code can’t be updated after manufacturing, so access gained through usbliter8 can survive software updates, device restores, and firmware revisions. Persistent access at the SecureROM level separates usbliter8 from a typical software vulnerability.
<\/p>\n The exploit doesn’t give attackers unrestricted access to user data. Apple’s Secure Enclave Processor remains separate from the vulnerability and provides an additional security boundary.
<\/p>\n Usbliter8 doesn’t directly compromise the Secure Enclave. The exploit could still expand the range of attacks available against other parts of Apple’s platform.
<\/p>\n The exploit also faces practical limitations. Researchers must have physical access to a device and use USB connectivity and DFU mode to carry out the attack.
<\/p>\n A new chapter after checkm8<\/p>\n![\"Diagram](\"https:\/\/www.newsbeep.com\/ie\/wp-content\/uploads\/2026\/06\/67990-143327-IMG_7642-xl.jpg\")
<\/a>A proper Setup transaction consists of two packets sent by the host. Image credit: Paradigm Shift<\/p>\n![\"Dark](\"https:\/\/www.newsbeep.com\/ie\/wp-content\/uploads\/2026\/06\/67990-143328-IMG_7641-xl.jpg\")
<\/a>The correct register values overwrite the ones the researchers corrupted. Image credit: Paradigm Shift<\/p>\n