Android security patch level

On this page 7

The Android security patch level is a date string in the YYYY-MM-DD format that declares which monthly Android Security Bulletin a device’s firmware fully addresses. In mobile security, it is the single most widely used indicator of how current a phone or tablet is against publicly disclosed vulnerabilities, and it appears in the settings app under the security or about-phone screens.

The value is set by the device manufacturer when it builds firmware and is stored in the system property ro.build.version.security_patch. A patch level of 2026-10-05, for example, asserts that every issue listed in the October 2026 bulletin up to that level has been fixed. The date says nothing about when the update was installed; it describes content, not timing.

How the patch level is defined and assigned

Google publishes the Android Security Bulletin on the first Monday of each month, listing vulnerabilities by CVE identifier, severity and affected component. Partners such as manufacturers and chipset vendors receive the details roughly one month in advance so they can prepare fixes before public disclosure.

Each bulletin defines two patch level strings. The first-of-month level covers the Android framework and platform components maintained in the Android Open Source Project, while the fifth-of-month level adds kernel and vendor components such as chipset drivers and firmware. The table below shows how the two levels differ.

Patch level stringScope of fixesWho usually supplies the code
YYYY-MM-01Framework, system services, media and AOSP librariesGoogle through AOSP
YYYY-MM-05Everything in -01 plus kernel and vendor componentsGoogle, chipset vendors, manufacturers
The two patch level strings in each bulletin

A device may only claim a date if it includes all fixes for that level and every earlier level. Claiming a later date while skipping a fix is a violation of partner requirements, although enforcement depends on testing rather than technical prevention.

The security patch level is only one of several update indicators on modern Android, and confusing them leads to wrong conclusions about device exposure. Since Project Treble and Project Mainline, parts of the system update through different channels on separate schedules.

IndicatorWhat it describesDelivery channel
Security patch levelBulletin fixes in system firmwareManufacturer over-the-air update
Vendor patch levelFixes in the vendor partitionManufacturer over-the-air update
Google Play system updateMainline modules such as media and networkingGoogle Play infrastructure
Android versionMajor platform release and API levelManufacturer over-the-air update
Google Play ProtectMalware scanning service statusGoogle Play services
Update indicators visible on an Android device

The vendor patch level, stored in ro.vendor.build.security_patch, can lag behind the system patch level on Treble devices. Security tools that read only the main property may therefore overstate protection of vendor drivers, which historically account for many critical issues.

Why the patch level matters for risk management

Attackers routinely reverse-engineer published fixes to build exploits for unpatched devices, so the gap between bulletin publication and installation is a measurable exposure window. Several bulletins each year include vulnerabilities flagged as under limited, targeted exploitation, which makes a stale patch level a concrete rather than theoretical risk.

Organizations use the date as an enforceable compliance signal. Mobile device management platforms and Android Enterprise policies can block access to corporate resources when the patch level is older than a defined threshold. The following table shows typical age bands and how security teams interpret them.

Patch level ageTypical assessmentCommon policy response
Under 30 daysCurrentFull access
30 to 90 daysAcceptable but agingWarning and update reminder
90 to 180 daysOut of compliance in many policiesRestricted access to sensitive data
Over 180 daysLikely unsupported or neglectedBlock access, plan device replacement
Typical interpretation of patch level age

Programs such as Android Enterprise Recommended require manufacturers to deliver security updates within 90 days of release for a stated support period, which gives buyers a contractual baseline rather than a hopeful expectation.

Checking and enforcing the patch level

Users find the value under Settings, Security and privacy or in the About phone screen, depending on the manufacturer interface. Administrators and developers can query it with Android Debug Bridge using adb shell getprop ro.build.version.security_patch, or programmatically through Build.VERSION.SECURITY_PATCH.

Enterprise tools collect the value through device attestation, which binds reported properties to hardware-backed keys. Attestation matters because a rooted or modified device can spoof the visible settings value, while hardware-backed attestation records the patch levels verified during boot.

MethodTypical userTrust level
Settings screenEnd userInformational only
ADB getpropDeveloper, support technicianCan be spoofed on rooted devices
Key attestation recordMDM and security platformsHardware-backed, highest
Ways to read the patch level

Limitations and common misconceptions

The patch level is an assertion by the manufacturer, not an independent audit. Research over the years has found devices that claimed recent dates while missing individual fixes, so the date is best treated as a strong indicator rather than proof.

  • A recent date does not cover manufacturer-specific code, which vendors patch through their own bulletins.
  • The installation date is irrelevant; a device updated yesterday may still carry a patch level from last year.
  • Mainline modules can be newer than the patch level, so the date may understate protection for those components.
  • End of support freezes the date, and the device then accumulates known vulnerabilities every month.
  • Custom firmware may set any date, so values from rooted devices or unofficial builds need extra scrutiny.

Despite these caveats, a current patch level remains the most practical baseline control for Android fleets, especially when combined with rooting detection, screen lock policies and mobile threat defense tools.

Understanding it simply

Every month, Google lists the known security holes in Android. The security patch level is a date on your phone that tells you which month’s list your phone has fixed. Think of it like the date on a vaccination record.

A date from the last month or two is good. A date that is many months old means your phone is missing known fixes, and criminals may already know how to use those holes. If your phone stops getting new dates, the maker has likely ended support.

Applied in practice

A hospital IT department manages about 1,200 Android phones used by nurses for messaging and patient lookup. Its mobile device management policy reads the patch level through hardware-backed attestation every day and flags any device older than 60 days.

After the policy goes live, the dashboard shows that 140 phones from one older model are stuck at a patch level more than eight months old, because the manufacturer has ended update support. The team restricts those phones to non-clinical applications, replaces them over the next quarter, and pushes pending updates to another 90 devices that simply had not rebooted. Within ten weeks, 98 percent of the fleet sits within the 60-day threshold, and the hospital passes its annual security audit without a mobile finding.