Google’s November 2026 Android Security Bulletin, published on November 2, fixes 208 flaws across the Framework, System, kernel and third-party silicon components.
The most severe is a critical Framework remote code execution (RCE) defect that needs no additional execution privileges and no user interaction.
The bulletin splits fixes across two patch levels, 2026-11-01 and 2026-11-05. This lets partners ship the cross-device platform fixes first. Google notified Android partners of all issues at least a month.
Google Fixes 208 Android Vulnerabilities
In Framework, CVE-2026-58868 (A-486464711) is rated Critical and typed RCE. It was fixed for Android 14, 15, 16, 16-qpr2, and 17. CVE-2026-58857 is a second Framework RCE, rated High.
The component also carries dozens of High-severity elevation of privilege (EoP), information disclosure, and denial-of-service (DoS) entries.
The System component holds two more Critical RCE entries, CVE-2026-58876 and CVE-2026-58936. Three Critical EoP entries sit beside them: CVE-2026-55275, CVE-2026-55283, and CVE-2026-58984.
CVE-2026-58814 and CVE-2026-58882 are Critical DoS. Zero-click RCE in Android’s System layer has recurred in recent bulletins, such as the May 2026 shell-level RCE in the System component.
The 2026-11-05 level covers kernel components. Its most severe entry is a remote EoP that needs no privileges or user interaction. Critical EoP entries span Bluetooth (CVE-2026-53256, CVE-2026-89774), pKVM (CVE-2026-59044, CVE-2026-59045) and HID (CVE-2026-80604).
CVE-2026-59048 is a Critical information disclosure in pKVM. High-severity kernel entries touch DMA buffers, FUSE, memory management, NFC, TLS, and Binder.
Several Framework and System fixes ship through Google Play system updates. These include Media Codecs (CVE-2026-58876), MediaProvider, WiFi, and Telephony components.
Mainline delivery can patch affected devices without a full OEM firmware release. The November 2025 zero-click RCE in the Android System component followed the same release pattern.
Chipset-specific entries carry severity ratings assigned by each vendor. MediaTek has eight Critical Modem entries: CVE-2026-20499, CVE-2026-20519, CVE-2026-20520 and CVE-2026-20545 through CVE-2026-20549. Qualcomm lists one Critical closed-source entry, CVE-2026-25285.
Arm’s CPU and Mali entries are rated High, as are twelve Imagination Technologies PowerVR-GPU entries. Unisoc lists High-severity Modem and uboot entries, including CVE-2026-80335 and CVE-2026-80336.
Modem-level defects matter because they sit below the Android framework. Earlier analysis of a UNISOC T612 baseband RCE over cellular video calls showed that framework patches do not mitigate baseband flaws.
Many vendor entries carry an asterisk, which means the bug details are not public. Their updates generally ship in the latest binary drivers for Pixel devices.
Device makers that include these updates set ro.build.version.security_patch to 2026-11-01 or 2026-11-05. Devices at 2026-11-05 or later include all applicable patches from this and previous bulletins.
Google says platform enhancements in newer Android versions make exploitation of many issues harder. Google Play Protect monitors for abuse and is enabled by default on devices with Google Mobile Services.
The severity ratings assume platform and service mitigations are disabled or bypassed. Source patches are due in the Android Open Source Project (AOSP) repository within 48 hours of publication, after which the bulletin will be revised with AOSP links.
AOSP now publishes source code only in Q2 and Q4, and android-latest-release always references the most recent push.
Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team
