Paradigm’s usbLITER8 jailbreak lets A12 and A13 iPhones bypass SecureROM
The BootROM exploit is immutable, so the only “fix” is new hardware, not new patches.

Security researchers at Paradigm Shift disclosed a newly disclosed BootROM exploit, dubbed “usbliter8,” that targets SecureROM on Apple devices with A12 and A13 chips. Because the flaw lives in immutable BootROM code, the affected models cannot be patched and the secure boot chain can be broken.
A newly disclosed BootROM exploit called “usbliter8” targets Apple devices with A12 and A13 chips, including iPhone XS, XR, 11, and 11 Pro, and it cannot be patched. The reason is brutally simple: the vulnerability sits in immutable BootROM code burned into silicon during manufacturing, so there is no software update that can rewrite it.
Paradigm Shift says exploitation works by attacking a flaw in the SecureROM code path tied to Apple’s use of the Synopsys DesignWare USB controller. In DFU mode, attackers can corrupt memory through certain USB setup packets, then gain control of SecureROM itself, which is the bottom of Apple’s “chain of trust.” If SecureROM is compromised, the attacker can interfere with everything that comes after it in the boot process.
For most iPhone owners, the headline should not trigger the classic “run to a panic button” reflex. The exploit requires physical access to a device and the ability to put it into DFU mode. That matters because it makes the bug the opposite of the kind of thing that shows up in phishing campaigns or drive-by attacks. In other words, this is not a “get pwned because you clicked something” story. It is a “you had the hardware in your hands, you chose DFU mode, now the secure boot floor has a crack” story.
But for security researchers, BootROM vulnerabilities are catnip. Unlike ordinary software flaws that disappear after the next patch rollout cycle, these hardware-rooted bugs remain exploitable for the lifetime of the affected devices. Paradigm Shift’s proof-of-concept is described as demonstrating the ability to run unsigned code during boot, load custom iBoot images without signature checks, and modify DFU behavior. The researchers also say compromised devices get marked with the familiar “PWND” string, a reference to jailbreaking history.
There are still limits on the scope. Paradigm Shift says Apple’s A11 chips dodge the issue because they use a different USB implementation. It also says A14 and later hardware appears to have fixed the conditions that make the exploit possible in the first place. So this is not “every iPhone, forever.” It is a specific slice of the device lineup, with A12 and A13 bearing the long-lived risk.
The really important systems detail is what SecureROM controls. SecureROM is positioned at the very bottom of Apple’s chain of trust, so controlling it is about as close as researchers can get to the “keys to the kingdom” without crossing the final boundary into Apple’s Secure Enclave Processor. The source notes that the exploit does not directly compromise the Secure Enclave Processor, which remains responsible for protecting passcodes, encryption keys, and other sensitive data. Still, gaining control of SecureROM shifts leverage upstream of sensitive-data protections, and that is why this still matters even if the Secure Enclave Processor is not directly breached.
From a product and governance standpoint, the lack of a patch is the point that lands hardest. Paradigm Shift disclosed the findings to Apple before publication and coordinated the release of the research with the company. Apple did not respond to The Register’s request for comment. Yet the practical outcome is that affected owners “can stop checking for patches now,” because there is no fix in the usual sense. The remedy is “simple, if somewhat expensive”: buy a new iPhone. That is the rare moment where the security lifecycle is constrained by manufacturing reality, not software agility.
For executives, boards, and investor-grade decision-makers watching the broader trust stack across mobile and embedded devices, the second-order lesson is about what “unpatchable” means operationally. If a root-of-trust component is compromised at the silicon layer, incident response becomes a hardware refresh problem, not a rollout problem. That changes the risk math for device strategy, update policy, and long-term support commitments across the entire ecosystem of chipmakers, OEMs, and platforms that rely on secure boot as a foundational guarantee.
This story's Key Insights and Take-aways are locked.
Create a free account to unlock Executive Actions for one credit.
Register to UnlockAlways free for Executives Club members. Join the Club
More in Technology

Export controls on cyber software failed for 30 years, even as Anthropic builds Mythos
A new model gets scrutiny, but the playbook of blocking cybersecurity software has historically underperformed, and the stakes are bigger now.

Langflow, LangGraph, LangChain get exploited via basic bugs, not “AI risk”
Check Point and other researchers show SQL injection, path traversal, and unsafe deserialization chain into remote code execution.

Aura’s e-ink photo frame makes “digital” feel old-fashioned again
Aura Ink uses e-ink to display rotating family photos in a way that visually escapes the “tech gadget” vibe.
