Both of the November 2025 patches have been provided in our regular non-security-preview releases for over a month, so we've already had the 2025-11-05 Android security patch level for over a month. Our patch level is set based on providing both the Android and Pixel security patches, so we're leaving it at 2025-11-01 until the Pixel stock OS release and Pixel Update Bulletin are published. The stock Pixel OS also included both November 2025 patches in early September. We expect they made a 2nd October release to ship the November carrier changes and will make a release in mid-November with patches from future Android Security Bulletins. All of the Android 16 security patches from the current December 2025, January 2026, February 2026 and March 2026 Android Security Bulletins are included in the 2025110601 security preview release. List of additional fixed CVEs: Critical: CVE-2025-48631, CVE-2026-0006 High: CVE-2022-25836, CVE-2022-25837, CVE-2023-40130, CVE-2025-22420, CVE-2025-22432, CVE-2025-26447, CVE-2025-32319, CVE-2025-32348, CVE-2025-48525, CVE-2025-48536, CVE-2025-48555, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2025-48567, CVE-2025-48572, CVE-2025-48573, CVE-2025-48574, CVE-2025-48575, CVE-2025-48576, CVE-2025-48577, CVE-2025-48578, CVE-2025-48579, CVE-2025-48580, CVE-2025-48582, CVE-2025-48583, CVE-2025-48584, CVE-2025-48585, CVE-2025-48586, CVE-2025-48587, CVE-2025-48589, CVE-2025-48590, CVE-2025-48592, CVE-2025-48594, CVE-2025-48596, CVE-2025-48597, CVE-2025-48598, CVE-2025-48600, CVE-2025-48601, CVE-2025-48602, CVE-2025-48603, CVE-2025-48604, CVE-2025-48605, CVE-2025-48609, CVE-2025-48612, CVE-2025-48614, CVE-2025-48615, CVE-2025-48616, CVE-2025-48617, CVE-2025-48618, CVE-2025-48619, CVE-2025-48620, CVE-2025-48621, CVE-2025-48622, CVE-2025-48626, CVE-2025-48628, CVE-2025-48629, CVE-2025-48630, CVE-2025-48632, CVE-2025-48633, CVE-2025-48634, CVE-2026-0005, CVE-2026-0007, CVE-2026-0008 2025110601 provides at least the full 2025-12-01 Android security patch level (a Pixel Update Bulletin for November 2025 hasn't been released could have fixes we don't get early, although it's likely empty) but will remain marked as providing 2025-11-01. View quoted note →

Linus Tech Tips tried out #GrapheneOS. Check it out:

When an individual acquires a zero-day and turns it into a product to be bought by people to freely target users of the vulnerable software, they are treated like a crook. When Cellebrite do it, it should be no different. Here is the statement from Cellebrite on the matter: “We do not disclose or publicize the specific capabilities of our technology. This practice is central to our security strategy, as revealing such details could provide potential criminals or malicious actors with an unintended advantage.” A software developer is entitled to know that their software is being / attempted to be exploited by a wealthy, influential actor. This is called responsible disclosure, a virtue of the security community these companies don't follow. What we do against these groups is an act of self-defence of our product and work. GrapheneOS, Google, Samsung, Apple and the greater mobile security community is neither a "potential criminal" or a "malicious actor". These authoritarian talking points are stale and come from the same playbook as "Think of the children" and other fallacy phrases meant to attack you as being a danger for something as simple as wanting to protect yourself. Vulnerabilities don't just exist for the bad guys. All vulnerabilities are to be patched when uncovered. At the bare minimum, a single so-called illicit use of it anywhere in the world immediately makes their exploit a cyberweapon that must be neutralised. Them being an exploit alone is the only justification we need to seek disrupting these threat actors' work. View quoted note →

Both patches in the November 2025 Android Security Bulletin have been included since our September 2nd release. It's now known that our 2025090200 and later releases provided the 2025-11-05 Android security patch level early due to shipping extra patches.

Android Open Source Project

Android Security Bulletin—November 2025 | Android Open Source Project

It's because these two patches were included in the full September 2025 bulletin patches we shipped but were made optional until November 2025. Later in September, we started our security preview releases able to provide Android Security Bulletin patches around 2-3 months early. Our security preview releases currently have the December 2025 and January 2026 patches. December 2025 has a huge set of patches due to being a quarterly patch level. January 2026 will likely be empty. We should have quarterly March 2026 patches to ship within a couple weeks. Due to having early access to the patches which we can use for our security preview releases, we've been able to determine that a subset were pushed to AOSP and other projects prior to the official embargo ending which means we'll be including those in our regular releases soon. Our security preview releases shipped all available December 2025 security patches in September 2025 and have continued adding the remaining patches. It should be frozen soon, but most of the patches have remained the same since September. Some were deferred to future bulletins. The new security patch system being used by Android is confusing for users and bad for the security of anyone not using #GrapheneOS with our security preview releases. We could have set the patch level string to 2025-11-01 in early September but in this case we didn't do that.

GrapheneOS has diminished exploit capabilities for Cellebrite a third time. They are no longer able to Full Filesystem extraction an unlocked device. This prevents extraction of hidden operating system and application data. Given it is unlocked, they're still accessing all the important stuff though. This could be an indicator of their target. They are likely to move their resources to attempt researching an exploit targeting the Titan M2 secure element or for extraction for AFU Locked devices rather than be concerned about extracting a device already unlocked. We routinely receive this information from sources familiar with Cellebrite. However, do you have more information on exploit vendors? Do the right thing. Tip off #GrapheneOS at security@ our domain or contact the project account on our platforms. We will respect your privacy. We have made upstream security reports to Google and Apple. Encryption can be performed via our Age public key: age1dcftzgq00ykgwvxl5te6d5clqgx75h2g54c0u8gjc43mcnea7p7q3ma0yx https://grapheneos.org/.well-known/security.txt View quoted note →

🙋 View quoted note →

A user on our community platforms submitted a grainy photo from a Cellebrite Premium sales pitch suggesting that they lost support for full filesystem extractions on *UNLOCKED* #GrapheneOS devices. This would mean that Cellebrite can no longer extract hidden operating system data or application data not available to the user when they know the users password. They are still unable to bypass the Titan M2 secure element backed brute force protections.

As GmsCompat (sandboxed Google Play compatibility later) development continues we get more compatibility with certain apps due to adding more workarounds with certain apps not working, like our recent fix with a shim for font loading. In the late future we could look at how to reduce the need to install any Google Play services implementations for apps, make them just work without any services, sandboxed or otherwise. Google Camera, Android Auto, and some others just work on GrapheneOS.

Wordle 1,589 5/6 ⬛🟨🟨⬛⬛ ⬛🟩⬛🟨⬛ ⬛🟩⬛⬛🟩 ⬛🟩⬛⬛🟩 🟩🟩🟩🟩🟩

Pixel Camera works without sandboxed Google Play services again with the GmsCompatLib version 100 update available in our App Store for GrapheneOS 2025102300 or later. The same changes will also be bundled in the next #GrapheneOS release, but this is our first out-of-band GmsCompatLib update which we'll be using to avoid needing OS releases to fix nearly any GmsCompat (sandboxed Google Play compatibility layer) related compatibility issues. It includes 2 fixes for other things too. View quoted note →

#GrapheneOS GmsCompatLib version 100 released. - extend shim for background service starts to address edge cases where a foreground service is required - add shim implementation of GmsFontProvider to prevent crashes of apps depending on Play services when it's missing or disabled (restores support for using Pixel Camera without Play services) - fix NoOpPrewarmService chain crash in Pixel Camera caused by lack of privileged OS integration

GitHub

Release lib-100 · GrapheneOS/platform_packages_apps_GmsCompat

Changes in version 100: add shim implementation of GmsFontProvider to prevent crashes of apps depending on Play services when it's missing or disa...

#GrapheneOS version 2025102200 released. • adevtool: add satellite eSIM overlays to avoid the special Skylo eSIM on 9th/10th gen Pixels being listed as a regular eSIM and being possible to erase with the regular eSIM erase functionality • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.111 • kernel (6.12): update to latest GKI LTS branch revision including update to 6.12.52 • System Updater: prevent reboot and security preview notifications from timing out after 3 days which is standard behavior since Android 15 QPR1 • System Updater: mark notification permission as fixed to prevent disabling overall notifications, but enable blocking progress, failure and already up to date notification channels • Sandboxed Google Play compatibility layer: add support for overriding BinderProxy transactions • Sandboxed Google Play compatibility layer: add support for out-of-band updates to GmsCompatLib • Vanadium: update to version 141.0.7390.111.0 • Vanadium: update to version 141.0.7390.122.0 • raise emulator super / dynamic partition size due to reaching the limit in some cases • adevtool: prefer prebuilt AOSP JDK 21 All of the Android 16 security patches from the current November 2025, December 2025 and January 2026 Android Security Bulletins are included in the 2025102201 security preview release. List of additional fixed CVEs: • Critical: CVE-2025-48593, CVE-2025-48631 • High: CVE-2022-25836, CVE-2022-25837, CVE-2023-40130, CVE-2024-43766, CVE-2025-22420, CVE-2025-22432, CVE-2025-32319, CVE-2025-32348, CVE-2025-48525, CVE-2025-48536, CVE-2025-48555, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2025-48567, CVE-2025-48572, CVE-2025-48573, CVE-2025-48574, CVE-2025-48575, CVE-2025-48576, CVE-2025-48577, CVE-2025-48578, CVE-2025-48579, CVE-2025-48580, CVE-2025-48582, CVE-2025-48583, CVE-2025-48584, CVE-2025-48585, CVE-2025-48586, CVE-2025-48587, CVE-2025-48589, CVE-2025-48590, CVE-2025-48592, CVE-2025-48594, CVE-2025-48596, CVE-2025-48597, CVE-2025-48598, CVE-2025-48600, CVE-2025-48601, CVE-2025-48602, CVE-2025-48603, CVE-2025-48604, CVE-2025-48605, CVE-2025-48609, CVE-2025-48612, CVE-2025-48614, CVE-2025-48615, CVE-2025-48616, CVE-2025-48617, CVE-2025-48618, CVE-2025-48619, CVE-2025-48620, CVE-2025-48621, CVE-2025-48622, CVE-2025-48626, CVE-2025-48628, CVE-2025-48629, CVE-2025-48630, CVE-2025-48632, CVE-2025-48633, CVE-2025-48634 2025100901 provides at least the full 2025-11-01 patch level and the Android 2025-11-05 patch level (Pixel Update Bulletin could have fixes we don't get early) but will remain marked as providing 2025-10-05.

Releases | GrapheneOS

GmsCompat (sandboxed Google Play compatibility layer in GrapheneOS) will have it's library signed with a separate key to allow for out-of-band updates. Should allow faster delivery of app compatibility fixes without waiting on new releases of GrapheneOS for the most part.

FYI: "Lockdown" button does not put an Android device BFU. It is still AFU, attack surface still applies. It just forces the user to use the primary credentials the next time. In GrapheneOS, the button "End Session" or "Power Off" is what you want.

Here is my scheduled corpo posting of a collage of software, now Please Buy My Fucking Products View quoted note →

Privacy is a human right. View quoted note →

Let me post cheesy one-liners like a pro-privacy product company real quick

Please don't get #GrapheneOS from weirdos on TikTok. You have no idea what your money would end up going to. It would likely be less productive than us using it to fund developer salaries and new deals. Anyways, here is how one of them replied to us when we told them to stop making pages selling a product claiming to be GrapheneOS. (Shit. I got cyber bullied...)

Also glad many of the startup 'just build' 'accelerate' San Francisco bros aren't here. A very creepy group. I guess I come from a different culture. View quoted note →

Twitter for you feed is so awful. Even after following accounts the recommendations stink.