The operating system is only one layer

Google’s November Pixel bulletin lists Critical elevation-of-privilege issues across bootloader, Trusty, pKVM and other device components. It also lists a Critical remote code execution issue in hardware codec firmware.

These findings show why a mobile security review must include the device patch level. Updating applications does not update firmware or boot components.

Use the vendor patch level as evidence

The Pixel bulletin says patch level 2026-11-05 or later addresses its listed issues and those in the November Android bulletin. Record the patch date and build for each managed device.

Do not use a generic Android version as proof that a device has received every Pixel firmware fix. Check the device’s security update field and the vendor’s release information.

Include phones in vulnerability management

Add mobile operating systems and firmware to the asset and patch process. Set an owner, expected update window and escalation path for devices that miss a release.

Remove business access from retired phones and confirm that old sessions, tokens and device certificates no longer work.