Android security update fixes no-click code execution
The November Android security update fixes a Critical vulnerability that could permit remote code execution (RCE), meaning an attacker could make a phone run their code from a distance, without the owner tapping or approving anything. Tracked as CVE-2026-58868, the flaw affects Android 14 through 17 and is covered by Android security patch level 2026-11-01 or later.
Phone manufacturers and mobile carriers distribute Android patches on their own schedules, so the update may not reach every eligible device at the same time. As of November 4, Google's bulletin reported no known attacks exploiting any of the listed vulnerabilities. None appeared in the Known Exploited Vulnerabilities catalog, the U.S. Cybersecurity and Infrastructure Security Agency list of security flaws confirmed as used in attacks, as of its November 3 update.
CVE-2026-58868 is described as a possible out-of-bounds write, in which software writes data beyond the memory space reserved for it. The underlying problem is a heap buffer overflow in the onOutputReceived function of FrameDecoder.cpp. A heap buffer overflow occurs when a program puts more data into a temporary area of memory than that area can safely hold. Neither Google's bulletin nor the CVE record explains how an attacker could reach the vulnerable code.
Google's Critical severity rating assumes that security protections built into Android and Google services have either been disabled or bypassed. Android 12 and 13 are not identified as affected by CVE-2026-58868, but Google's records do not establish whether those older releases contain the flaw.
Users can check their protection by opening Settings, selecting About phone or About tablet, and then choosing Android version. That screen shows dates for both the Android security update and the Google Play system update. For CVE-2026-58868, the relevant entry is the Android security update. A date of 2026-11-01 or later includes fixes for this flaw and the other November vulnerabilities in the Framework, System and Android runtime, the components that provide core phone services and run Android applications.
A patch level of 2026-11-05 or later includes every correction in the November bulletin. That broader level also covers flaws in the kernel, the central software that controls hardware and system resources, as well as components supplied by Arm, Imagination Technologies, MediaTek, Unisoc and Qualcomm. Google uses two patch dates so manufacturers can distribute fixes shared by all Android devices sooner, while encouraging them to include the complete bulletin.
Devices running Android 10 or later can receive some security corrections through Google Play system updates. The November list for that channel contains another Critical vulnerability, CVE-2026-58876. However, CVE-2026-58868 is not included there, so users must check the Android security update date rather than relying on the Google Play system update date. The bulletin provides no workaround for a phone that cannot yet install the required update.
A separate Critical flaw, CVE-2026-58882, may enable remote denial of service without user interaction. A denial-of-service attack makes a device or service unavailable rather than necessarily taking control of it. The flaw is in decodeWapPdu, a function that processes WAP Push messages delivered through SMS text messaging. A researcher published an October 29 analysis titled “SMS of Death” concerning a bug in the same function, although neither the bulletin nor the CVE record confirms that the reported bug and CVE-2026-58882 are the same issue.
According to that analysis, one malformed WAP Push message can crash com.android.phone, the Android process responsible for phone functions, and terminate an active call, including an emergency call. Tests on several phone models reportedly produced the crash every time. An attacker would need only the target's telephone number, and the harmful message would not appear in the inbox. Because the phone retries processing it after startup, the device can repeatedly crash while starting until the message is removed. A proof-of-concept app, software published to demonstrate that a flaw can be triggered, is publicly available. The researcher also said Android 12 and 13 use the same code but do not receive the correction supplied to newer releases.
Google's November bulletin contains 216 vulnerabilities, including 23 rated Critical. CVE-2026-58876 and CVE-2026-58936, both in Android's System component, are two additional Critical flaws that could permit remote code execution. Six Critical vulnerabilities affect the kernel, including two in Bluetooth code. The most severe kernel issue could let a remote attacker obtain elevated privileges, meaning greater control over the device, without user interaction.
The 2026-11-05 patch level also addresses Critical vulnerabilities in MediaTek modem code and a closed-source Qualcomm component, whose underlying program code is not publicly available. MediaTek describes its Critical modem issues as out-of-bounds writes and says it is unaware of active exploitation. For businesses treating mobile patching as part of wider IT risk, AEU-I offers security-first IT, infrastructure and consulting.
Because CVE-2026-58868 requires no action from the phone owner and has no published workaround, installing the Android security update is the direct protective step. Users should verify the displayed patch date rather than assuming that a general system update or Google Play system update includes this particular fix.