Google published its August 2026 Android security bulletins on August 4, 2026, and every supported Google device will receive an update to the 2026-08-05 patch level, according to the company's own security documentation (documented). The Pixel Update Bulletin for August 2026 adds Google-device fixes on top of the month's platform-wide Android Security Bulletin.
What ships in the August 2026 update?
Two documents define the month. The Android Security Bulletin lists vulnerability fixes for the platform itself, and the Pixel Update Bulletin lists additional patches that ship only on Google hardware. The Pixel bulletin states that patch levels of "2026-08-05 or later address all issues in this bulletin and all issues in the August 2026 Android Security Bulletin," and adds that all supported Google devices will receive the update, per the Pixel bulletin on Google's Android documentation.
The cadence is deliberately routine. Android's security model runs on monthly patch trains: Google publishes fixes for the core platform, then device makers integrate them into their own builds on their own schedules. Google's hardware gets the tightest loop, since the same company writes the bulletin and ships the update, which is why Pixel devices reach the newest patch level first and most predictably.
The scale of each month's cycle varies, and Google's bulletins deliberately do not dramatize it. Fixes are grouped and described technically, severity is documented by the platform team, and the practical instruction to users is the same every month: accept the update when it arrives. The August 2026 cycle is notable mainly for what it maintains rather than anything it adds.
Which patch levels matter?
Android reports two dated patch levels for the month, and the newer one is the complete set. The platform bulletin states that "security patch levels of 2026-08-01 or later address all issues associated with the 2026-08-01 security patch level and all previous patch levels," per the August 2026 Android Security Bulletin. Device manufacturers that include the fixes set the patch string themselves, which is the mechanism that lets one bulletin surface as different build numbers across the ecosystem.
| Patch level | What it addresses | Who sets it |
|---|---|---|
| 2026-08-01 | All issues in the August 2026 platform bulletin plus all previous levels | Device manufacturers integrating the fixes |
| 2026-08-05 | Everything above, plus all Pixel-specific fixes in the August device bulletin | Google, on supported Google devices |
The split exists because platform code and vendor code ship on different cycles. A phone can carry the platform fixes but lag on vendor ones, and the two-level scheme makes that state visible instead of hidden inside an opaque build number. For buyers comparing devices, patch-level transparency is one of the few security facts that can actually be checked in a store.
How do users check they are protected?
The check is short. Open Settings, find the security patch level in the About section, and confirm it reads 2026-08-05 or later on a supported Google device. Google's documentation encourages all customers to accept the updates, and notes that Google device firmware images are also available on the Google Developer site for users who flash builds manually.
Users on other manufacturers' hardware apply the same check with the platform level and their maker's rollout calendar, since the same fixes spread outward at different speeds. Support windows decide the rest: a device outside its update window stops receiving this class of fix entirely, which makes the August cycle a useful annual prompt to check whether a phone is still covered at all.
