Threat reportVulnerabilityTL-2026-5077
iPhone BootROM Flaws (checkm8 CVE-2019-8900, usbliter8) Could Be Used to Undermine Cryptocurrency Wallet Security
Unpatchable Apple SecureROM (BootROM) flaws - checkm8 (A5-A11, iPhone X and earlier) and usbliter8 (A12/A13, disclosed June 22, 2026 by Paradigm Shift) - let an attacker with physical USB access to a device in DFU mode execute code before iOS loads. First disclosed .
Key facts for checkm8 BootROM exploit
| Identifiers | TL-2026-5077, CVE-2019-8900 |
|---|---|
| Also known as | checkm8, usbliter8, Apple SecureROM BootROM exploits |
| Severity | MEDIUM |
| CVSS | 6.8 (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| First disclosed | |
| Exploitation status | Public proof-of-concept exploit |
| EPSS | CVE-2019-8900: 68.5% (99.3th percentile) |
| Affected products | Apple SecureROM (BootROM) on A5-A11 SoCs - iPhone 4S through iPhone X, iPad, iPod touch, Apple Watch, Apple TV (checkm8); Apple SecureROM (BootROM) on A12/A13 SoCs - iPhone XS, XR, 11 family, SE 2nd gen, Apple Watch S4/S5 (usbliter8) |
| Weaknesses (CWE) | CWE-94 |
| Tools | 34306/usbliter8-fun, Pimoroni TINY2350, Raspberry Pi Pico 2 (RP2350), Waveshare RP2350 USB-A, Waveshare RP2350 Zero, checkm8, usbliter8 |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1542 Pre-OS Boot, T1553 Subvert Trust Controls |
| Motivation | UNKNOWN |
| Target sectors | finance, cryptocurrency, consumer, government administration |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 11 cited sources |
Detection coverage for checkm8 BootROM exploit
As of 2026-11-02, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-5077 across Splunk SPL, Microsoft KQL and Sigma, covering 12 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Apple Device in DFU Mode Enumerated on Host — checkm8/usbliter8 Exploitation Precondition
TL-2026-5077: Detects an Apple device enumerating in DFU mode (USB VID 05AC / PID 1227) via Windows Security 6416 PnP events. DFU mode is the mandatory precondition for the unpatchable SecureROM exploits checkm8 (CVE-2019-8900, A5-A11) and usbliter8 (A12/A13), which send crafted USB setup packets to the DFU stack before iOS loads. Behaviour-first: fires on the device state, not on a tool name.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1542, T1068, T1211
- Data sources: windows_security, wineventlog:Security EventCode 6416 (Audit PNP Activity)
- Severity: medium
- Confidence: medium
Splunk SPL
index=wineventlog sourcetype="WinEventLog:Security" EventCode=6416 earliest=-24h | where match(_raw,"(?i)VID_05AC&PID_1227") OR match(_raw,"(?i)Apple Mobile Device .DFU Mode.") | stats count min(_time) as first_seen max(_time) as last_seen by host | eval first_seen=strftime(first_seen,"%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen,"%Y-%m-%d %H:%M:%S") | table host count first_seen last_seenMicrosoft KQL
DeviceEvents
| where Timestamp > ago(24h)
| where ActionType == "PnpDeviceConnected"
| extend d = parse_json(AdditionalFields)
| extend DeviceId = tostring(d.DeviceId), DeviceDescription = tostring(d.DeviceDescription), ClassName = tostring(d.ClassName)
| where (DeviceId contains "VID_05AC" and DeviceId contains "PID_1227") or DeviceDescription contains "Apple Mobile Device (DFU Mode)"
| project Timestamp, DeviceName, DeviceId, DeviceDescription, ClassName, InitiatingProcessAccountName
| order by Timestamp descSigma
title: Apple Device Enumerated in DFU Mode on Windows Host (checkm8 / usbliter8 Precondition)
id: 3f1c8a52-7b0e-4d6a-9c41-5e2a7d9b1a01
status: experimental
description: Detects an Apple device (USB VID 05AC, PID 1227) enumerating in DFU mode on a monitored Windows host. DFU mode is the required precondition for the SecureROM exploits checkm8 (CVE-2019-8900) and usbliter8.
references:
- https://kb.cert.org/vuls/id/941987/
- https://nvd.nist.gov/vuln/detail/CVE-2019-8900
- https://github.com/prdgmshift/usbliter8
author: AII-Detector — ThreadLinqs Intelligence
date: 2026-11-02
tags:
- attack.defense-evasion
- attack.persistence
- attack.privilege-escalation
- attack.t1542
- attack.t1068
- attack.t1211
- cve.2019-8900
logsource:
product: windows
service: security
detection:
selection_event:
EventID: 6416
selection_id:
DeviceId|contains: 'VID_05AC&PID_1227'
selection_desc:
DeviceDescription|contains: 'Apple Mobile Device (DFU Mode)'
condition: selection_event and (selection_id or selection_desc)
falsepositives:
- Authorized restore or recovery of iPhones by IT or repair staff
- Mobile forensics lab workstations
level: medium
Known false positives:
- Authorized iPhone restore/recovery by IT, repair or MDM staff
- Mobile forensics or device-provisioning workstations that legitimately use DFU mode
Tuning notes: Enable Audit PNP Activity (Security 6416). Allowlist provisioning/forensics hosts by host or asset tag and alert only on hosts outside that set; enrich with asset owner and raise priority when the host also shows exploit tooling (KQL-001) or an RP2350 boot device (SIG-001).
- BootROM Exploit Tooling Execution — checkm8 / usbliter8 / ipwndfu / gaster · unlock with TL Creds
- USB-Tunnelled SSH to Jailbroken iOS Device (iproxy / ssh -p 2222) · unlock with TL Creds
- Web Proxy Access to usbliter8 PoC Repository · unlock with TL Creds
- RP2350 Microcontroller BOOTSEL Device Attached — usbliter8 Exploit Hardware · unlock with TL Creds
- iOS Keychain / App Container Data Pulled over SSH After BootROM Exploit · unlock with TL Creds
- Python pyusb Script Targeting Apple DFU Device (0x05ac:0x1227) · unlock with TL Creds
- Unsigned/Modified Boot Components Loaded via DFU Tooling (iBSS/iBEC/im4p) · unlock with TL Creds
- usbliter8 PoC Repository Retrieval via Command Line · unlock with TL Creds
Indicators of compromise for checkm8 BootROM exploit
As of 2026-11-02, Threadlinqs Intelligence tracks 12 indicators of compromise for TL-2026-5077.
How checkm8 BootROM exploit works
A public PoC runs from a Raspberry Pi Pico 2 (RP2350). Encrypted user data and the Secure Enclave are not directly compromised, so wallet seed theft would require additional vulnerabilities.
Apple's SecureROM (BootROM) is the first code the application processor executes at boot. It lives in read-only silicon and cannot be updated by software patches. Two publicly known flaws in its USB Device Firmware Upgrade (DFU) handling allow an attacker with physical access to run unsigned code before iOS loads.
checkm8 (CVE-2019-8900, CERT/CC VU#941987) was publicly disclosed on September 27, 2019 by the researcher axi0mX. It is a use-after-free in the SecureROM USB DFU stack and affects devices with A5 through A11 SoCs (iPhone 4S through iPhone X, plus iPads, iPod touch, Apple Watch and Apple TV models with those chips). NVD scores it CVSS 3.1 6.8 MEDIUM (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-94). Exploitation requires the device to be connected to a host and placed in DFU mode; changes are not persistent across a reboot. CERT/CC states there is no practical patch and that device replacement is the only guaranteed mitigation.
usbliter8 was disclosed on June 22, 2026 by Paradigm Shift, a European security firm, with PoC code published at github.com/prdgmshift/usbliter8. It targets Apple A12 and A13 SoCs (iPhone XS, XR, 11 family, SE 2nd generation, and Apple Watch S4/S5 per SecurityWeek). It chains a USB controller bug with a device firmware configuration weakness; crafted USB setup packets trigger an out-of-bounds write that gives control before the OS loads, allowing unsigned boot components to be loaded and bypassing Apple's code verification. Public demonstrations used a Raspberry Pi Pico 2 (RP2350) as the USB exploit device; tested boards include Waveshare RP2350 USB-A, Waveshare RP2350 Zero and Pimoroni TINY2350. A related public demonstration booted a jailbroken iOS 27 beta build on an iPhone 11 Pro using an RP2350-based Pico 2, building on earlier work by wh1te4ever. A14/S6 and newer chips are unaffected, per Apple.
Cybersecurity News (November 2, 2026) frames these flaws as a risk to cryptocurrency wallet security. The exploits do not directly compromise the Secure Enclave, and encrypted user data stays behind additional barriers (passcode-derived keys, Data Protection). Stealing a wallet seed phrase would need further vulnerabilities, decrypted-data access, or attacks on remaining protections. Researchers note such exploits are highly useful to forensics vendors. No in-the-wild exploitation, threat actor, or malware is reported in the sources. Severity is analyst-assigned for usbliter8, which has no CVE in the sources.
MITRE ATT&CK techniques by tactic:
Collection
Defense Evasion
Persistence
defense-impairment
Remediation for checkm8 BootROM exploit
Patches
- No patch is possible: the flaws reside in read-only BootROM (CERT/CC VU#941987). Install current iOS updates to address other vulnerabilities, but they cannot rewrite the BootROM
Immediate actions
- Keep affected devices (A5-A13: iPhone X and earlier, XS, XR, 11 family, SE 2nd gen) under physical control; do not leave them unattended or hand them to untrusted parties
- Use a strong alphanumeric device passcode and strong wallet passwords so encrypted data stays behind additional barriers
- If physical compromise or seed phrase exposure is suspected, move funds to a new wallet with a freshly generated seed
- Do not rely on airplane mode alone as a protection
Workarounds
- Device replacement is the only guaranteed mitigation for checkm8 per CERT/CC
- Restrict physical USB access to devices; use MDM lost mode and remote wipe for lost or stolen devices
Longer-term hardening
- Migrate high-value wallet use to A14/S6 or newer devices, which Apple states are unaffected by usbliter8
- Prefer hardware wallets or dedicated secure devices for large cryptocurrency holdings
- Add physical-access and unauthorized USB/DFU-mode events to device-loss and insider-threat procedures
Affected and fixed versions
- Apple — SecureROM (BootROM) on A5-A11 SoCs - iPhone 4S through iPhone X, iPad, iPod touch, Apple Watch, Apple TV (checkm8)
Vulnerable versions: A5; A6; A7; A8; A9; A10; A11 - Apple — SecureROM (BootROM) on A12/A13 SoCs - iPhone XS, XR, 11 family, SE 2nd gen, Apple Watch S4/S5 (usbliter8)
Vulnerable versions: A12; A13; S4; S5
Fixed in: A14/S6 and newer not affected
Timeline of checkm8 BootROM exploit
- Researcher locked-ioc-11 publicly discloses locked-ioc-10, a SecureROM USB DFU use-after-free affecting A5-A11 devices (CVE-2019-8900).
- CERT/CC publishes VU#941987 stating no practical patch exists and device replacement is the only guaranteed mitigation.
- CERT/CC last revises VU#941987.
- NVD publishes CVE-2019-8900 with CVSS 3.1 base score 6.8 MEDIUM (AV:P) and CWE-94.
- (Date approximate: reported as recent after the locked-ioc-9 disclosure; exact date not stated.) Public demonstration boots a jailbroken iOS 27 beta (build 24A5370h) on an iPhone 11 Pro using an RP2350-based Raspberry Pi Pico 2, building on locked-ioc-8's earlier work.
- Apple states A14/S6 and newer are unaffected and that the exploit cannot bypass data protection or directly access user information.
- locked-ioc-7 discloses locked-ioc-9, a BootROM exploit for A12/A13 (and S4/S5) chips, and releases PoC code on GitHub (prdgmshift/locked-ioc-9).
- Cybersecurity News reports the BootROM flaws could be used to undermine cryptocurrency wallet security; direct seed theft would require additional vulnerabilities.
Sources cited for checkm8 BootROM exploit
- CERT/CC VU#941987 - Apple SecureROM use-after-free (checkm8) CERT/CC · Advisory · 2019-09-27
- NVD - CVE-2019-8900 NVD (NIST) · Advisory · 2025-02-21
- Usbliter8 Exploit - The Apple Wiki theapplewiki.com · Research · 2026-06-22
- checkm8 Exploit - The Apple Wiki theapplewiki.com · Research · 2019-09-27
- Paradigm Shift usbliter8 PoC repository GitHub · Proof of concept · 2026-06-22
- Lookout - checkm8 iOS vulnerability lookout.com · Blog · 2019-09-30
- Zimperium analysis of checkm8 zimperium.com · Blog · 2019-10-03
- Hackers Could Exploit iPhone BootROM Flaws to Compromise Cryptocurrency Wallet Security cybersecuritynews.com · News · 2026-11-02
- New Exploit Bypasses Apple's Boot Defenses, Affects Millions of iPhones (SecurityWeek) SecurityWeek · News · 2026-06-22
- Booted jailbroken iOS 27 on iPhone 11 Pro (Cybersecurity News) cybersecuritynews.com · News
- The Hacker News - bootrom jailbreak iOS exploit The Hacker News · News · 2019-09-27
Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated —.