GrapheneOS, Pixel Titan M2 and commercial forensic tools: what the public record shows
Dated, source-attributed summary of GrapheneOS and Pixel security features and reported forensic-vendor support matrices. Point-in-time, not a guarantee.
Updated
In short
As of 2026-10-29, the GrapheneOS features page and FAQ document an auto-reboot timer (18-hour default), charging-only USB-C port control when locked, and secure-element delays on failed attempts; the project's 2026-07-26 statement says the reboot returns the device to BFU. CyberSecureFox and Hackmag reported, from a leaked October 2025 Cellebrite support matrix, that GrapheneOS access was limited to builds predating late 2022 and that stock Pixel 6 to 9 devices were extractable in BFU, AFU and unlocked states without passcode brute force; Android Authority described BFU access on stock Pixels as limited and GrapheneOS results only up to 2022 or 2023 patch levels, so these secondary reports differ on patch dates. On 2026-08-05 the project said that, as of roughly two months earlier, Cellebrite had not been able to exploit a locked GrapheneOS device for around four years, and that Cellebrite's recent documentation shows its latest successful exploit against one was a 2022 release; these are project claims, with no independent publication of that documentation cited. The guide notes that nothing it cites supports calling any device "uncrackable", and that the sources reporting vendor matrices do not independently test attacks outside such a matrix, such as a known or coerced passcode (Google's Pixel 6 blog separately says an independent lab assessed the Titan M2 chip).
Scope and caveats
This guide records what is publicly documented about GrapheneOS and Pixel security hardware and what leaked or reported forensic-vendor documents have said about them. Three limits apply throughout. First, vendor support matrices are point-in-time snapshots; forensic capabilities change with each OS release and each exploit. Second, several sources below are the GrapheneOS project's own statements, which are attributed as claims. Third, nothing here supports calling any device "uncrackable": the same sources describe exploits against stock Pixels and older GrapheneOS builds, and none of them independently tests attacks outside the scope of a vendor matrix, such as a known or coerced passcode.
What GrapheneOS documents
The GrapheneOS features page and FAQ describe, as of 2026-10-29:
- Auto-reboot. A timer starts when the device locks and the device reboots if no successful unlock occurs before it expires. The default is 18 hours, configurable from 10 minutes to 72 hours or off. The features page says the timer does not apply in BFU; the project's 2026-07-26 statement, linked below, says a reboot returns the device to BFU.
- USB-C port control. Five modes (off, charging-only, charging-only when locked, charging-only when locked except before first unlock, on). The default is charging-only when locked.
- Duress PIN/password. Entering it wherever device credentials are requested irreversibly wipes the device and any installed eSIMs.
- Hardware-backed throttling. The FAQ says the secure element (Titan M on Pixels) is an input to key derivation and enforces delays: no delay for failed attempts 1 to 4, one minute at attempt 5, four hours at attempt 10, 41 days at attempt 15, and no further attempts after 20.
- Exploit protection. Hardened memory allocation and hardware memory tagging for slab allocations, which GrapheneOS describes as probabilistic detection of use-after-free and inter-object overflows.
In a project statement dated 2026-07-26, GrapheneOS adds that its supported devices' secure element requires the Owner user to authenticate before its firmware can be updated, to stop a coerced firmware update from removing rate limiting, and that by default it blocks new USB connections at a software and hardware level while locked. It also says GrapheneOS does not depend on the duress feature to protect data, and that it raises the password length limit from 16 to 128 characters so a long passphrase need not rely on secure-element rate limiting.
What Google documents
Google's Pixel 6 announcement (2021-10-27) describes Titan M2 as a discrete security chip designed by Google with an in-house RISC-V processor, tested against the AVA_VAN.5 vulnerability-assessment level by an independent accredited lab, and supporting Android StrongBox for keys that protect PINs and passwords. A 2018 post describes insider-attack resistance on the Pixel 2: the secure hardware checks the password, limits the rate of checks, and is designed so that even properly signed malicious firmware cannot be installed on the security module of a lost or stolen device without the user's password; forcing an upgrade wipes the secrets that decrypt user data.
The AOSP Weaver documentation says the Weaver HAL arrived in Android 8.1 and gives a secure interface for lock-screen credential verification. The rate-limiting page says Android 16 QPR2 and higher apply significantly stronger rate-limiting policies. These documents describe design intent, not the outcome of any specific attack.
Reported vendor matrices, by date
April 2024 documents (reported July 2024). 404 Media reported on 2024-07-17 that leaked Cellebrite documents dated April 2024 showed it could not unlock a sizeable share of modern iPhones. AppleInsider relayed that, as of that document, AppleInsider's list of models it said could not yet be unlocked on iOS 17.4 or later named the XR, XS, 11, SE (2nd and 3rd gen), 13, 14 and 15 families and did not list the iPhone 12, with the iPhone 12 to 14 ranges listed "Coming soon" for iOS 17.1 to 17.3.1. The same documents covered Android. 404 Media's Android detail is behind a paywall, so for GrapheneOS this guide relies on the project's own reading, posted 2024-07-18: that the documents showed Cellebrite could not exploit a locked GrapheneOS device unless it had not been patched since mid-2022. GrapheneOS also said the tables showed Pixel 6 and later and iPhone 12 and later stopping Cellebrite's brute-force attacks through their secure elements, while earlier secure elements had been exploited.
October 2025 Teams-call leak. 404 Media reported on 2025-10-30 that someone joined a Cellebrite call on Microsoft Teams and leaked a screenshot of a support matrix covering Pixel phones, including GrapheneOS. Android Authority (2025-10-30) reported that every locked Pixel 9 running GrapheneOS was listed as inaccessible, and that older GrapheneOS devices showed only partial results up to 2022 or 2023 security patch levels. CyberSecureFox (2025-11-03) and Hackmag (2025-11-05) reported, in similar terms, that stock Pixel 6 to 9 devices were extractable in BFU, AFU and unlocked states without passcode brute force (Android Authority describes the BFU access on stock Pixels as limited; the matrix covered Pixel 6 to 9 and did not list Pixel 10), and that GrapheneOS access was limited to builds predating late 2022. These secondary reports differ on exact patch dates, and none of them is the leaked slide itself.
GrapheneOS statements after that. On 2025-10-31 the project said Pixels and iPhones both stop Cellebrite's brute-force attacks but neither had stopped its BFU, AFU or full-file-system exploits without GrapheneOS. On 2026-08-05 it said that, as of roughly two months earlier, Cellebrite had not been able to exploit a locked GrapheneOS device for around four years, and that Cellebrite's recent documentation showed its latest successful exploit against a locked GrapheneOS device was against a version released in 2022 (second post). No independent publication of those 2026 tables is cited here, so treat these as project claims. The project also said on 2026-09-08 that exploit developers, naming Cellebrite and NSO, are using AI tools and currently hold a major advantage, which it expects "will likely be turned into a major disadvantage over the long term". Treating old tables as stale is this guide's own inference.
Vendors are aware of the OS. Magnet Forensics' GK200 Graykey Examinations course lists an Android anti-forensics module with attention to GrapheneOS, its supported devices and its data-wipe behaviour.
What this means for examiners
- Treat every matrix as dated. Ask the vendor for current written support for the exact model, build and lock state, and test before relying on it. See choosing a mobile forensics tool.
- Record the OS build and patch level first; the reported matrices key on them.
- Expect time limits: at default settings GrapheneOS reboots a locked device to BFU if no successful unlock occurs within 18 hours (configurable from 10 minutes to 72 hours, or off), and stock devices may reboot after about 72 hours of inactivity on iOS 18.1 or later and after three days on Android where Google Play services applies it; defaults vary by device and software version (BFU vs AFU).
- On GrapheneOS at default settings, expect new USB data connections to be refused while locked; stock devices vary. Note that credentials entered in any prompt could trigger a duress wipe if the user configured one.
- Absence of a capability in a vendor matrix is not evidence about other routes, such as consent, cloud data or known credentials.
What this means for users
- GrapheneOS's own analysis is that sophisticated attackers do not break disk encryption directly: they either exploit the OS in the AFU state or brute-force the PIN or password. The reported matrices are consistent with that picture, but it is the project's interpretation, not an independent finding.
- A short PIN depends heavily on rate limiting. GrapheneOS states that a typical PIN or password can easily be brute-forced without secure-element rate limiting, and its features page says it supports passphrases of up to 128 characters.
- A matrix describes a vendor's tooling on a date. It does not describe coercion, legal compulsion or future exploits.
- Updates matter: both the leaked rows and the project's statements are tied to patch levels.
Sources
- GrapheneOS, Features
- GrapheneOS, FAQ (encryption and brute-force delays)
- GrapheneOS forum, GrapheneOS protections against data extraction from locked devices (2026-07-26, edited 2026-08-03, project statement)
- Google Security Blog, Pixel 6: Setting a new standard for mobile security (2021-10-27)
- Android Developers Blog, Insider Attack Resistance (2018-05-31)
- Android Open Source Project, Weaver
- Android Open Source Project, Rate-limiting
- 404 Media, Leaked Docs Show What Phones Cellebrite Can (and Can't) Unlock (2024-07-17)
- AppleInsider, Cellebrite can't crack iPhones running iOS 17.4 or later (2024-07-18)
- 404 Media, Someone Snuck Into a Cellebrite Microsoft Teams Call and Leaked Phone Unlocking Details (2025-10-30)
- Android Authority, Cellebrite leak highlights how much more secure Pixel phones are with GrapheneOS (2025-10-30)
- Hackmag, Leak reveals which Pixel phones are vulnerable to Cellebrite tools (2025-11-05)
- CyberSecureFox, Leaked Cellebrite Briefing (2025-11-03)
- GrapheneOS on Mastodon, reading of April 2024 Cellebrite documents (2024-07-18, project statement)
- GrapheneOS on Mastodon, secure elements and brute force (2024-07-18, project statement)
- GrapheneOS on Mastodon, Pixels, iPhones and Cellebrite exploits (2025-10-31, project statement)
- GrapheneOS on Mastodon, locked GrapheneOS and Cellebrite (2026-08-05, project statement)
- GrapheneOS on Mastodon, Cellebrite documentation and 2022 versions (2026-08-05, project statement)
- GrapheneOS on Mastodon, AI-assisted exploit development (2026-09-08, project statement)
- GrapheneOS on Mastodon, PINs and secure-element rate limiting (2026-07-27, project statement)
- Magnet Forensics training, GK200 Graykey Examinations (course description, vendor)