Join our Newsletter — 33% off our NHI Course
Home› Guides› Android and Pixel Security Update Support: Versions, Devices…
Guide Vulnerability Management

Android and Pixel Security Update Support: Versions, Devices and Guaranteed Dates

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 20 November 2026 14 min read
On this page

Every Android phone stops receiving security fixes at some point, and the date depends on who made it: Google states a guarantee window for each Pixel model, while other manufacturers publish their own policies. This tracker sets out what Google's own pages say about Pixel update windows, how the monthly Android Security Bulletin and patch levels work, how to check a device, and how to run a fleet so that phones past their window do not keep access to company data and identities.

The page is deliberately limited to what Google publishes. For non-Pixel Android devices, Google's own guidance is to contact the manufacturer or carrier, and that is the rule this page follows: no dates are given for other brands here. For the wider lifecycle picture across servers and desktops, see the Operating System End of Life and Extended Support Guide; for managing the devices themselves, see the Android Enterprise Security Guide.

Status as of 20 Nov 2026: per Google's Pixel update page, Pixel 8 and later get 7 years of Android version and security updates, Pixel Fold and the Pixel 7 and 6 series get 5 years, and Pixel 5a with 5G and earlier no longer receive Android version updates or security updates. The latest Android Security Bulletin is November 2026 (published 2 November 2026, updated 6 November 2026).

Key takeaways

  • Google states Pixel support as a number of years from the date the device first became available on the Google Store in the US, not as a fixed calendar end date per model.
  • Pixel 8 and later: 7 years of Android version updates and security updates. Pixel Fold, Pixel 7 series and Pixel 6 series: 5 years.
  • Pixel 5a with 5G, Pixel 5, Pixel 4a (5G), Pixel 4a, Pixel 4, Pixel 3a, Pixel 3, Pixel 2 and the original Pixel no longer receive Android version updates or security updates.
  • Android Security Bulletins are published on the first Monday of each month (the following work day if that Monday is a holiday). A device's security patch level, shown in Settings, tells you how current it is.
  • The November 2026 bulletin states that security patch levels of 2026-11-05 or later address all of its issues, and that devices with Android 10 and later may receive security updates.
  • For other Android brands, update schedules vary by device, manufacturer and carrier; take dates only from that manufacturer's own policy.
  • Use the security patch level, not the Android version number, as the compliance signal in device management and conditional access.

How Google states Pixel update support

Google's Pixel help page "Learn when you'll get software updates on Google Pixel phones" groups devices into three bands. The wording matters, because it defines what you can and cannot put in an asset register.

  • Pixel 8 and later. Google states that these phones "will get updates for 7 years starting from when the device first became available on the Google Store in the US". The same 7 years applies to Android version updates and to security updates.
  • Pixel Fold, Pixel 7 and Pixel 6 series. Google states that these phones "will get updates for 5 years starting from when the device first became available on the Google Store in the US".
  • Pixel 5a and earlier. Google states that these phones "no longer receive Android version updates and security updates".

The help page itself does not list calendar end dates. Instead it links to a second Google page that gives the month each model became available on the US Google Store. The window therefore runs from that month for the stated number of years. Google's page does not say what happens on a device after its 7 or 5 year window ends, so this tracker does not speculate about it; treat a device at the end of its window as one that may stop receiving fixes at any time and confirm on the device itself.

Two practical points follow from the wording. First, the start point is US availability, so a device bought later, or bought in another country, does not get a longer window. Second, a refurbished or second-hand device inherits the model's window, which is often shorter than its owner assumes.

Pixel support table

The table below takes the US Google Store availability month and the guarantee length from Google's two Pixel help pages, read on 20 Nov 2026. The "window ends" column is NHI Mgmt Group arithmetic (availability month plus the stated number of years); Google does not publish it as a date, so confirm against the device and Google's page before you rely on it for a contract or audit.

DeviceUS Google Store availabilityAndroid version and security updatesWindow ends (arithmetic, not a Google date)Status on 20 Nov 2026
Pixel 11, 11 Pro, 11 Pro XL, 11 Pro FoldAugust 20267 yearsAugust 2033Supported
Pixel 10aMarch 20267 yearsMarch 2033Supported
Pixel 10 Pro FoldOctober 20257 yearsOctober 2032Supported
Pixel 10, 10 Pro, 10 Pro XLAugust 20257 yearsAugust 2032Supported
Pixel 9aApril 20257 yearsApril 2032Supported
Pixel 9 Pro, 9 Pro FoldSeptember 20247 yearsSeptember 2031Supported
Pixel 9, 9 Pro XLAugust 20247 yearsAugust 2031Supported
Pixel 8aMay 20247 yearsMay 2031Supported
Pixel 8, 8 ProOctober 20237 yearsOctober 2030Supported
Pixel FoldJune 20235 yearsJune 2028Supported
Pixel 7aMay 20235 yearsMay 2028Supported
Pixel 7, 7 ProOctober 20225 yearsOctober 2027Supported
Pixel 6aJuly 20225 yearsJuly 2027Supported
Pixel 6, 6 ProOctober 20215 yearsOctober 2026Listed by Google in the 5 year band; window reached by arithmetic. Confirm patch level on device
Pixel 5a with 5GAugust 2021None nowEndedNo longer receives updates
Pixel 5, Pixel 4a 5GOctober 2020None nowEndedNo longer receives updates
Pixel 4aAugust 2020None nowEndedNo longer receives updates
Pixel 4, 4 XLOctober 2019None nowEndedNo longer receives updates
Pixel 3a, 3a XLMay 2019None nowEndedNo longer receives updates
Pixel 3, 3 XLOctober 2018None nowEndedNo longer receives updates
Pixel 2, 2 XLOctober 2017None nowEndedNo longer receives updates
Pixel, Pixel XLOctober 2016None nowEndedNo longer receives updates

The Pixel 6 and 6 Pro row is the one to watch this quarter. Google's page still places them in the 5 year band, and the arithmetic puts the end of the window in October 2026. Rather than guess whether a further update will arrive, check the security patch level on those handsets each month: if it stops moving while newer Pixels advance, treat the device as unsupported.

Android Security Bulletins and patch levels

Google publishes the Android Security Bulletin on the first Monday of each month; if that Monday is a holiday, publication moves to the following work day. Google's bulletin overview also notes quarterly bulletins in March, June, September and December, and separate bulletins for Pixel updates, Pixel Watch, Chromecast, Android Automotive OS, Android Wear and Android XR. The Android Security Bulletin itself covers platform fixes, upstream Linux kernel fixes and fixes from system on chip manufacturers.

Recent bulletins listed on Google's overview page:

BulletinPublishedPatch level
November 20262 November 20262026-11-01
October 20265 October 20262026-10-01
September 20268 September 20262026-09-01
August 20263 August 20262026-08-01
July 20266 July 20262026-07-01
June 20261 June 20262026-06-01

Each bulletin uses two patch level strings. The November 2026 bulletin labels its first group of issues as the 2026-11-01 security patch level and states that "security patch levels of 2026-11-05 or later address all of these issues". In practice, a device reporting the later string for a month has every fix in that month's bulletin; a device reporting the earlier string has the first group. The bulletin does not give a fuller definition, so keep your policy to that plain reading.

The same bulletin states that devices with Android 10 and later may receive security updates as well as Google Play system updates. Its tables carry an "Updated AOSP versions" column, and in November 2026 the versions listed include Android 14, 15, 16, 16 QPR2 and 17, with not every issue applying to every version. Google does not, on these pages, publish an end date for each Android version number. That is why the version number on its own is a poor control: two phones on the same Android version can sit months apart in patch level, depending on the manufacturer.

Google also states on its bulletin landing page that, starting in 2026, source code is published to the Android Open Source Project in Q2 and Q4. That affects teams who build custom Android images, not most enterprise fleets.

Non-Pixel Android devices

For Android devices other than Pixel, Google's help page tells users to contact the manufacturer or carrier, and notes that update schedules vary by device, manufacturer and mobile carrier. This tracker therefore does not list dates for other brands. A sound process for a mixed fleet is:

  1. For each manufacturer you allow, find its own published security update policy and record the URL and the date you read it.
  2. Record the model's stated update window and start point exactly as the manufacturer words it. If the wording is a number of years from launch, record the launch date the manufacturer gives, not a retailer's.
  3. Where a manufacturer publishes no end date, say so in the register instead of inventing one, and set a review date.
  4. Treat carrier-locked variants as separate entries, because carriers can add delay between a manufacturer's release and the handset.
  5. Track the observed patch level per model each month. A model whose patch level stops moving is unsupported in practice, whatever the policy page says.

How to check a device

Google's "Check and update your Android version" help page gives the steps:

  1. Open the device's Settings app.
  2. Tap About phone or About tablet, then Android version.
  3. Read the Android version, the Android security update (the patch level), the Google Play system update and the build number.

For a fleet, the same values are reported to your device management console. Collect three fields per device: model, Android version and security patch level. Then compare the patch level against the current month's bulletin. A patch level more than one or two months behind the current bulletin is a stronger warning sign than an old Android version number.

Fleet policy and access control

The security risk of an out of window phone is not only the phone. Mobile devices hold mail sessions, single sign-on refresh tokens, authenticator apps, passkeys, VPN profiles and certificates, and they often hold API tokens for business apps. A handset that no longer gets fixes keeps those credentials in an environment that can no longer be repaired.

  • Set a patch level floor. Define a maximum age for the security patch level (for example, no older than the bulletin from two months ago) and enforce it in device management and in conditional access rules. NHI Mgmt Group suggests the patch level rather than the model, because it catches both out of window devices and in window devices that are simply not updating.
  • Block out of window models at enrolment. Keep an allow list of models whose update window has more than a year left, using the table above for Pixel and each manufacturer's policy for others.
  • Plan replacement against the window. For Pixel, the window end month is known from the day of purchase. Put it in the asset register when the device is issued, and order replacements before it arrives.
  • Revoke, do not just retire. When a device leaves service, revoke its sessions, remove its passkeys and authenticator registrations, revoke device certificates and wipe it. Retiring a phone without revoking what it holds leaves live credentials behind.
  • Watch bring your own device. Personal phones are often older models. Apply the same patch level floor to app protection or work profile access, so that an unsupported personal phone cannot reach company data.
  • Treat exploited vulnerabilities as urgent. When a bulletin fixes an issue listed in the CISA Known Exploited Vulnerabilities Catalog, shorten the patch level grace period for that month.

Guidance on profiles, compliance rules and enrolment is in the Mobile Device Management Security Guide, and on-device settings for individual users are covered in the Android Security and Privacy Settings Guide.

Where identity fits

Phones are identity devices. They carry the second factor for human accounts, and increasingly they run apps that hold long-lived tokens for non-human identities: field service apps with API keys, developer tools with cloud credentials, and messaging bots signed in on a work handset. An unsupported phone is therefore a credential store with a known expiry on its defences.

  • Bind access to device health: issue tokens only to devices that meet the patch level floor, and re-check on refresh, not only at sign-in.
  • Prefer phishing-resistant methods held in hardware-backed storage, and re-enrol them when a user moves to a new phone instead of copying secrets across.
  • Inventory apps on managed phones that hold API keys or service credentials, and rotate those credentials when the device is replaced.
  • Record the device as the owner of any certificate or key it holds, so that the asset retirement process triggers revocation automatically.

Common failure patterns

  • Using Android version as the control. Version numbers say nothing about how recent the fixes are. Patch level does.
  • Counting the window from purchase. Google counts Pixel windows from first US Google Store availability, so a phone bought a year after launch has a year less than its owner thinks.
  • Inventing dates for other brands. Registers that copy dates from forums or retailers drift from the manufacturer's policy. Record only the manufacturer's own wording.
  • Retiring devices without revoking credentials. Sessions, passkeys, certificates and app tokens stay valid after the phone is put in a drawer.
  • Exempting executives and personal phones. The oldest handsets in a fleet often belong to the people with the widest access.
  • Ignoring carrier delay. Carrier variants can lag the manufacturer; measure observed patch levels, not promised ones.

Practitioner checklist

  • Record model, Android version and security patch level for every managed Android device.
  • Add the Pixel availability month and window length to the asset register at issue, with the source URL and the date read.
  • For each non-Pixel manufacturer allowed, store the URL of its own update policy and the date read; record "no end date published" where that is the case.
  • Set and enforce a patch level floor in device management and conditional access.
  • Review the Android Security Bulletin each month after its first Monday release and update the floor.
  • Block enrolment of Pixel 5a with 5G and earlier, and of any model with less than a year of window left.
  • Check Pixel 6 and 6 Pro patch levels monthly and move them to the unsupported list when updates stop.
  • On retirement, revoke sessions, passkeys, authenticator registrations, certificates and app tokens before wiping.
  • Apply the same floor to personal devices that reach company data.

Standards and references

Related NHI Mgmt Group resources: Android Enterprise Security Guide · Operating System End of Life and Extended Support Guide · Mobile Device Management Security Guide · Patch Management Guide

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 20 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org