Android November 2026 bulletin: 216 flaws and zero-click RCE
Google fixes 216 Android vulnerabilities, 23 critical: CVE-2026-58868 in Framework allows RCE with no user interaction. Patch level to reach: 2026-11-05.

On 2 November 2026 Google published the November Android security bulletin. According to the count by INCIBE-CERT and Cybersecurity360, it fixes 216 CVEs: 23 rated critical and 193 high on Android’s own severity scale (SecurityWeek speaks of «two dozen» critical issues). The most severe, CVE-2026-58868 in the Framework component, can lead to remote code execution with no additional privileges and no user interaction. The bulletin was also covered by heise Security, The Hacker News, Security Affairs, the Latvian CERT (CERT.LV) and the Canadian Centre for Cyber Security (advisory AV26-1128).
According to Security Affairs, Google is not aware of active exploitation of the flaws in the bulletin; INCIBE-CERT’s table reports «no exploitation» for all critical CVEs.
Two patch levels
As every month, the fixes ship in two blocks:
- 2026-11-01: according to SecurityWeek, 119 flaws in Android runtime, Framework (65) and System (53). Seventeen of them had already been delivered ahead of time through Google Play system updates.
- 2026-11-05: 97 flaws in the kernel and in components from Arm, Imagination Technologies, MediaTek, Unisoc and Qualcomm. More than a dozen are critical: Bluetooth, pKVM, HID, MediaTek modem and a Qualcomm closed-source component.
Only patch level 2026-11-05 or later covers every fix in the bulletin. The versions listed by INCIBE-CERT for the AOSP components are Android 14, 15, 16, 16-qpr2 and 17, depending on the CVE.
On the same day Google also published the Android XR and Wear OS bulletins: according to SecurityWeek, in addition to the Android bulletin flaws, the former fixes one high-severity Framework flaw and the latter two high-severity flaws in Framework and System.
Technical details
Remote code execution with no interaction
- CVE-2026-58868 (Framework): heap buffer overflow in the
onOutputReceivedfunction ofFrameDecoder.cpp, allowing an out-of-bounds write. It is fixed from patch level 2026-11-01 on Android 14 to 17, as Security Affairs and CERT.LV confirm. - CVE-2026-58876 and CVE-2026-58936 (System): use-after-free, in system components and in
png_set_tRNSrespectively; these too can lead to remote code execution with no interaction.
Elevation of privilege and denial of service (System)
- CVE-2026-55275 and CVE-2026-55283: use-after-free with possible remote elevation of privilege;
- CVE-2026-58984: memory corruption with local elevation of privilege;
- CVE-2026-58814 and CVE-2026-58882: integer overflows in message handling, with remote denial of service. CVE-2026-58882 concerns the
decodeWapPdufunction, which processes WAP Push messages delivered over SMS. ARX News has already covered it in connection with the «SMS of Death»: Security Affairs notes, however, that neither the bulletin nor the CVE record explicitly confirms that it is the same flaw described by the researcher.
Kernel (patch level 2026-11-05)
- Bluetooth: CVE-2026-53256 and CVE-2026-89774, connections used without properly keeping references to their sockets;
- pKVM (protected Kernel-based Virtual Machine): CVE-2026-59044 and CVE-2026-59045, memory and concurrency errors with local elevation of privilege, and CVE-2026-59048, out-of-bounds read with information disclosure;
- HID: CVE-2026-80604, insufficient validation of report size, classified by Android as elevation of privilege.
According to Security Affairs, the most severe kernel flaw allows a remote attacker to gain elevated privileges with no user interaction; the source does not say which one it is.
MediaTek modem and Qualcomm
- Eight critical flaws in MediaTek modems (CVE-2026-20499, CVE-2026-20519, CVE-2026-20520, CVE-2026-20545, CVE-2026-20546, CVE-2026-20547, CVE-2026-20548, CVE-2026-20549): out-of-bounds writes that, according to INCIBE-CERT, can allow elevation of privilege when the device connects to a base station controlled by the attacker. MediaTek’s own bulletin, Security Affairs reports, describes six of them, attributing them to missing bounds checks, integer overflow or improper input validation, and reports no exploitation.
- CVE-2026-25285: Qualcomm closed-source component, critical; the bulletin publishes no technical details.
In the MITRE ATT&CK Mobile matrix these flaws fall mainly under Exploitation for Privilege Escalation (T1404) and Endpoint Denial of Service (T1642). There are currently no public indicators of compromise.
Impact on businesses
The main risk is the combination of zero-click flaws and long rollout times: updates come from manufacturers and carriers, with delays that vary from model to model. For a mixed corporate fleet this means that, for weeks, part of the devices will remain exposed.
- Corporate smartphones and tablets have access to email, VPN, authenticator apps and documents: remote code execution on the device is an entry point into company systems.
- The MediaTek modem flaws require a fake base station: it is a targeted scenario, relevant for people who travel or work in sensitive settings.
- Devices running Android 13 or earlier do not appear among the versions listed in the bulletin.
- In healthcare, tablets and smartphones used on wards and by on-call staff are often managed separately and updated late.
For NIS2 entities, mobile devices are part of asset inventory and vulnerability management: a patch level stuck for months on devices with access to company data is a risk to document and treat.
What to do now
- Measure the patch level of all Android devices from your mobile device management console. The target is 2026-11-05; for CVE-2026-58868 alone, 2026-11-01 is enough. On a single device: Settings › About phone › Android version, which shows the dates of the Android security update and of the Google Play system update (guidance from CERT.LV).
- Install updates as soon as the manufacturer makes them available and ask your suppliers for timelines for the models in use, including those with MediaTek modems.
- Set a compliance rule: devices below a defined patch threshold cannot reach email, VPN and business applications until they are updated.
- Replace or isolate out-of-support devices (Android 13 or earlier, or models the manufacturer no longer updates), starting with those of critical roles and healthcare staff.
- Include Wear OS and Android XR in your inventory, if used in the company.
- Keep track of developments: no source reports exploitation, but for zero-click flaws a public exploit would quickly change priorities.
Last updated:


