Opening the Apple Watch Black Box

01 / The offsiteWhy I chose this target

The stations showed me how hardware questions connect to software: a solder joint can decide whether I can see a signal, while firmware remains code I can study even when the vendor publishes no download. Hardware interfaces and secure boot reveal what runs before the operating system, while rehosted fuzzing lets me use familiar software techniques against extracted code.

I could not master any station in a day, but I learned what to ask: Where does a device first run code? Which component decides whether to trust the next one? Where does data move between processors? Which interfaces are for users, service staff, or the factory?

Apple publishes a high-level security model, but I found much less work on modern Watch internals than on the iPhone or Mac. Together with its dense hardware, iPhone dependency, and proprietary protocols, that gap makes the Apple Watch hard to inspect.

02 / MethodMapping the Series 11 as a target

I started by identifying the Watch as model A3337, the 46 mm cellular Series 11. I then used TechInsights teardown report DDT-2511-814 to map its internal hardware. The report provides board photographs, X-rays, component names, antenna measurements, package analysis, and the removal sequence.

I also read Apple’s current Series 11 specifications and the watchOS 26 sections of the Apple Platform Security guide, which describe Apple’s stated security model. To compare those claims with public evidence, I reviewed primary sources: conference talks, papers, source code, Apple security advisories, and reports by their authors.

Each source answers a different question: a product page lists Apple’s claims, while a teardown shows whether a chip or antenna exists. A security guide describes planned controls, while an exploit or protocol implementation shows what its author proved. I used them together because no single source answers every question.

Here, a finding means a conclusion supported by evidence, not a new vulnerability. I mark uncertain component names and do not apply old results to Series 11 without evidence.

03 / The deviceWhat is inside the Series 11

The research target is the Jet Black aluminum cellular model with a black sport band. Apple lists an S10 system-in-package (SiP), 64 GB of storage, Wi‑Fi 4, Bluetooth 5.3, second-generation Ultra Wideband (UWB), and NFC for Apple Pay. Cellular models A3335 and A3337 also support 5G RedCap and LTE.

Setup starts on an iPhone 11 or later running iOS 26.

The teardown names the S10 package APL1W15 and shows that it contains an application-processor die and a separate power-management die. An SK Hynix package combines 2 GB of LPDDR5 memory with 64 GB of 3D NAND. The report also identifies a MediaTek cellular package with its own baseband, RF transceiver die, and 256 MB of LPDDR4, but TechInsights marks the exact modem part as uncertain, so I treat it as likely, not Apple-confirmed.

The separate modem changes how I think about the target because its own memory suggests that it runs firmware, parses cellular data, and exchanges messages with the application processor. The teardown confirms only the package and memory, so I could not determine its firmware design, update path, isolation model, or message formats.

For a small device, the Watch has many radios: cellular, Wi‑Fi, Bluetooth, Ultra Wideband, NFC, dual-frequency satellite positioning, wireless charging, and a 60 GHz transceiver. The teardown maps separate paths for these systems, including three main cellular antennas and shared antennas for Wi‑Fi, Bluetooth, GPS, and UWB.

The report confirms a 60 GHz transceiver and antenna. I found no source for their protocol, purpose, session model, or access path, so I left their role open.

Adhesive holds the dense main board in place, so reaching it requires opening the Watch from the display side and removing screws and covers. The sensor board connects inside the case, while glue holds the charging coil to the rear glass. Because the report identifies no debug interface, I may have to open the case and change the electrical or mechanical conditions I want to study, which makes physical access costly and hard to repeat.

04 / ArchitectureThe Watch is a trust graph

The Watch can act as a companion, an independent network client, a payment device, a sensor, or a key for another device, and I treat each role as a separate relationship to test.

The paired iPhone is the Watch’s main trust relationship; Apple’s security guide says initial pairing between iOS 26 and watchOS 26 uses Internet Key Exchange version 2 (IKEv2). The animated Watch pattern authenticates a shared secret, while manual PIN pairing derives a connection secret with SPAKE2+, a password-authenticated key exchange.

Apple adds the post-quantum ML‑KEM‑1024 scheme to elliptic-curve Diffie–Hellman (ECDH). The Watch and iPhone then exchange Ed25519 public keys and Bluetooth Low Energy (BLE) pairing secrets, and the Watch roots its private keys in the Secure Enclave. Later IKEv2/IPsec sessions use ML‑KEM‑768 with ECDH, and AES‑256‑GCM protects the traffic.

Bluetooth, Wi‑Fi, and cellular can carry the authenticated IPsec traffic between the phone and Watch, but WatchWitch found flaws in Apple’s extensions around that tunnel.

The iPhone also stores the Watch backup, which Apple’s backup guide says the phone includes in its iCloud or computer backup. Only iCloud backups and encrypted computer backups include Health and Fitness data, while the Watch backup omits payment cards, the Watch passcode, and Bluetooth pairings. Evidence can therefore span the Watch, iPhone, cloud, and app services.

The Watch can reach services without the phone nearby because independent apps can contact their servers, cellular models can reach the network directly, and the phone can sync saved Wi‑Fi credentials to the Watch. Although the iPhone remains central, some network traffic bypasses it.

05 / DefencesWhat Apple documents

Boot and executable code

Apple’s security guide describes secure boot, signed updates, and hardware-backed operating-system integrity on Apple Watch. Apple requires a signature on every watchOS executable, validates and signs third-party code, and limits embedded libraries. On S4 through S10, Apple lists Kernel Integrity Protection, firmware protection, pointer authentication, and Page Protection Layer rules that prevent changes to verified executable memory.

Although the guide does not describe the S10 boot ROM flow, Watch trust caches, full sandbox profiles, or repair-service path, the documented controls still give me tests. The system should accept only signed code, protect verified executable pages, and stop a kernel bug from making unsigned code persistent.

Two secure chips with different jobs

The Secure Enclave and Secure Element have different jobs: Apple documents a Secure Enclave in every Watch since Series 1; it runs separately from the application processor and manages secrets, lock state, passcode delays, and authorization. It also has its own secure boot and protected memory, while a hardware path lets it confirm the side-button press used for Apple Pay even if an attacker controls software on the application processor.

The Secure Element stores payment credentials, handles payment cryptography, and turns a payment card into a device-specific account number. The Secure Enclave confirms the user’s identity and button press, while the Secure Element creates the transaction cryptogram. This split limits what one compromised processor can do, so I would test the authorization messages between them.

Data at rest

Apple says the Watch encrypts each file with its own key and groups files into protection classes, while the Secure Enclave manages the keybag and lock state that control access to those keys. Apple lists the broad classes but does not map every Series 11 database and app file to one.

The Secure Enclave enforces passcode retry delays across restarts, and after enough failed attempts, the Watch locks and must reconnect to its paired phone. Because Apple’s documentation does not confirm that every Watch follows the iPhone’s optional “erase after ten attempts” setting, I do not assume it.

Updates and recovery

Apple must sign and approve normal updates; its approval includes anti-replay data and covers Secure Enclave software separately. Apple can stop signing old versions and warns that users cannot downgrade Apple Watch after an update, while a nearby unlocked iPhone can recover a Watch on the restore screen. This signed consumer flow can restore the Watch but gives me no public debug access.

06 / Attack surfaceWhere the Watch accepts input

The attack surface includes every place where the system accepts input or makes a security decision. Some surfaces accept internet traffic, while others require a nearby radio, a malicious app, the paired phone, physical access, or stolen keys; these access needs affect how practical an attack is.

watchOS is still a networked operating system

My first instinct was to focus on exotic hardware attacks, yet ordinary software still handles much of the untrusted input. Apple’s watchOS 26.5 advisory covers image and media parsing, APFS, IOKit, kernel memory safety, mDNS, Wi‑Fi, WebKit, privacy controls, sandbox escape, and sensitive storage. The list shows which code handles untrusted input; it does not prove that an updated Series 11 is exploitable.

In FORCEDENTRY, Citizen Lab captured an iMessage zero-click exploit against an iPhone, and Apple confirmed that the malicious-PDF flaw affected Watch Series 3 and later. Shared Apple services and parsers can therefore expose watchOS even when attackers first target another device.

Apps create their own trust graphs

watchOS supports watch-only, companion, and independent apps: a companion app can exchange queued or immediate messages with its iPhone app, while an independent app can contact a server directly. HealthKit grants access by data type and separates read from write access, while Keychain sharing requires signed entitlement groups.

watchOS enforces privacy differently from iOS, and the 2025 LANShield research showed that watchOS lacked the iOS local-network privacy prompt. A proof-of-concept Watch app reached local devices and attacked a router with default credentials, and Apple still lists local-network privacy as unsupported on watchOS. Although the flaw was in the router, the Watch gave the app an unexpected route to it.

The phone-Watch link above Bluetooth and Wi‑Fi

The 2025 WatchWitch project mapped the modern phone-Watch link by reversing the proprietary stack and building enough of it to connect an Apple Watch to Android. Bluetooth and Wi‑Fi feed a common IP layer, while application traffic travels through an authenticated IPsec tunnel and Apple protocols above it carry notifications, proxy traffic, state, and Health data.

WatchWitch found that a proprietary link-management extension accepted messages before IKEv2 authentication. This let an attacker redirect or disrupt traffic but not read useful data without the keys; Apple fixed the issue in watchOS 10.3 after the WatchWitch disclosure.

The project also found that an extra Health-data layer used AES-CBC without authentication, which could let an attacker already inside the IPsec tunnel alter a sample type if they knew some plaintext. Apple did not classify the issue as exploitable.

WatchWitch did not report a break in IKEv2 or IPsec; its findings were in Apple’s link-management messages and extra Health-data layer.

NFC, UWB, 5G, and 60 GHz

Apple documents the NFC payment path in detail: the NFC controller talks to the Secure Element, which can handle payment credentials without the application processor, while the side button records the user’s intent. I found no public report of a modern NFC relay or payment-key attack on Series 11.

Series 11 uses Apple’s second-generation UWB system, but the Ghost Peak team showed distance-reduction attacks only against earlier Apple U1 devices such as iPhones and AirTags. They did not test Series 11, so I cannot say whether the attack affects this Watch.

I found less Watch-specific research on the cellular path than on Bluetooth or Wi‑Fi, even though the separate modem package and memory add firmware and protocol surfaces. Apple’s specifications list 5G RedCap, a simpler 5G profile for small devices. Classen and colleagues studied Apple’s application-processor-to-baseband interface and baseband diagnostics on the iPhone, but their results do not tell me how the Series 11 baseband behaves.

Health data is both local and distributed

The Watch records sensitive daily data such as heart rate, movement, workouts, location, sleep, medications, and body measurements. Apple uses Data Protection and per-type HealthKit permissions, but a sample can still cross several systems. The Watch has its own HealthKit store and may remove old samples to save space, while the paired iPhone keeps a longer history that may then enter iCloud or an encrypted computer backup.

McGee’s forensic study shows why a record’s source matters. A Health sample can record its app, device, timestamps, and other details, but it cannot prove who wore the Watch or why an event occurred. WatchWitch also found deletion records on older systems that kept the sample type and deletion time. watchOS 26 may behave differently.

07 / HistoryThe public research record

Early work produced full jailbreaks for Watches that shared much with iPhones of the same age, while newer work reaches modern Watches through the paired phone, backups, shared parsers, apps, and network protocols. I found no public full jailbreak for Series 11.

Apple also offers researchers no supported low-level Watch access: its Security Research Device program covers only iPhones, and its Watch bounty flags provide no shell access.

08 / SynthesisWhat I learned

The target includes the phone and cloud

Both devices hold pairing state: backups pass through the phone, Health history can remain there after the Watch removes old samples, and apps may split their logic among the Watch, iPhone, and a server. For these reasons, I would not test the Watch in isolation.

Several computers share the case

The S10 runs watchOS and apps, while the Secure Enclave guards secrets and authorization, the Secure Element handles payment credentials, and a separate modem likely runs vendor firmware. Radio controllers and sensor processors add more code and state, so a watchOS version does not describe the firmware running on every processor in the case.

Test Apple’s custom protocols

WatchWitch found problems in unauthenticated management messages and an extra Health-data layer that point me toward the custom messages and state around the standard protocols.

Access limits what I can test

Early jailbreaks provided a shell, kernel memory, and filesystem access, but I found no such public path for Series 11. The teardown identifies no diagnostic connector, the boards are tightly packed, and Apple signs recovery images, so without controlled low-level access, I have to confirm chip names and trace messages through indirect evidence.

09 / LimitsWhat I still do not know

I need answers to six questions before I can make stronger claims about Series 11.

• The exact S10 secure-boot flow, debug-disable state, kernel integrity design, sandbox profiles, and entitlement map.
• The Series 11 DFU, factory, service, and post-failure recovery protocols.
• The 5G modem firmware, application-processor interface, memory protections, reset model, and update trust chain.
• The purpose and reachable protocol of the 60 GHz transceiver.
• The security of second-generation UWB on Series 11.
• The file-level Data Protection classes and a repeatable way to acquire the modern filesystem.

These are unanswered research questions, not vulnerability claims; I need enough access to observe the system before I can trust a negative result.

The offsite taught me to look for the first code that runs and every point where one component trusts another; the Series 11 showed me that its case is only one part of the target because the paired iPhone, radios, secure chips, modem, and cloud all matter.

I can now map those links, but I still cannot observe the code and state inside a modern Watch. A repeatable way to inspect its boot process and firmware would turn many of the open questions above into tests; until then, I will treat claims about unseen Series 11 internals as hypotheses, not results.

SourcesPrimary references

1. TechInsights. Apple Watch Series 11 5G 46mm Deep Dive Teardown, report DDT-2511-814, 17 November 2025.
2. Apple. Apple Watch Series 11 technical specifications.
3. Apple Platform Security. System security for watchOS, updated 28 January 2026.
4. Apple Platform Security. The Secure Enclave and Secure intent.
5. Apple Platform Security. App code signing process and Data Protection overview.
6. Apple Support. Backing up Apple Watch and restoring Apple Watch with an iPhone.
7. Apple. About the security content of watchOS 26.5, 11 May 2026.
8. Max Bazaliy. Jailbreaking Apple Watch, DEF CON 25, 2017.
9. tihmstar. jelbrekTime, public Series 3 developer-jailbreak source, 2018.
10. Citizen Lab and Google Project Zero. FORCEDENTRY captured in the wild and technical analysis, 2021.
11. Elcomsoft. Analyzing Apple Watch Series 3 file system, 2022.
12. James McGee. Forensic analysis of Apple Health data, 2023.
13. Nils Rollshausen et al. WatchWitch: Interoperability, Privacy, and Autonomy for the Apple Watch, PoPETs 2025; source code.
14. Moritz Contag et al. LANShield: Protecting LAN Devices from Insecure Applications, PoPETs 2025.
15. Paradigm Shift. Introducing usbliter8 and public proof of concept, June 2026.
16. iFixit. Apple Watch Series 7 teardown and the removed diagnostic connector, 2021.
17. Leu et al. Ghost Peak: Practical Distance Reduction Attacks Against HRP UWB Ranging, USENIX Security 2022. The work did not test Series 11.
18. Classen et al. ARIstoteles: Fuzzing Apple’s Baseband Interface, 2026. The work studied iPhone paths, not Apple Watch.