top of page

Android’s November Update: A Critical Flaw That Needs No Click

Nov 11
3 min read


Most people think of phone attacks as needing a mistake, such as tapping a bad link or installing a shady app. Some of the most serious Android bugs need nothing of the kind, and Google’s November security bulletin includes one of them.


The headline flaw

Google patched CVE-2026-58868, a critical flaw that could let an attacker run code on a phone remotely without any user interaction. It affects Android 14 through 17 and is fixed with security patch level 2026-11-01 or later. Technically, it is an out-of-bounds write caused by a heap buffer overflow in a function called onOutputReceived, inside the file FrameDecoder.cpp. Neither Google’s bulletin nor the CVE record explains how an attacker would reach that code. Google’s critical rating also assumes that Android’s built-in protections and Google’s services are turned off or bypassed, so the real-world risk may be lower than the label suggests.


As of November 4, the bulletin reported no attacks exploiting any of its flaws, and none were in CISA’s Known Exploited Vulnerabilities catalog as of its November 3 update. Older versions such as Android 12 and 13 are not listed as affected, although Google’s records do not say whether they contain the flaw.


A big bulletin

The November bulletin lists 216 vulnerabilities, 23 of them rated critical. Two more critical flaws, CVE-2026-58876 and CVE-2026-58936, could allow remote code execution and sit in Android’s System component. Six critical flaws are in the kernel, two of them in Bluetooth code, and the most severe kernel bug could let a remote attacker gain elevated privileges without any user interaction. The later patch level also fixes critical problems in MediaTek modem code and in a closed-source Qualcomm component. MediaTek says it is not aware of any active exploitation of its flaws.


The “SMS of Death” connection

Another critical flaw, CVE-2026-58882, could allow a remote denial-of-service attack with no user interaction. It is in decodeWapPdu, a function in the code that handles WAP Push messages delivered by SMS. On October 29, a researcher known as Mark B published a write-up called “SMS of Death” about a bug in the same function, though neither the bulletin nor the CVE record confirms they are the same bug.


According to that write-up, a single malformed message crashes the phone process and ends any active call, including emergency calls, and it crashed every time in tests on several phone models. The attacker needs only the target’s phone number, and the message never appears in the inbox. Because the phone retries the message at startup, it can keep crashing until the message is removed. A proof-of-concept app is public, and the researcher says Android 12 and 13 run the same code but do not receive the newer fix.


How to check your phone

Open Settings, tap About phone (or About tablet), then Android version, and look for the dates of the Android security update and the Google Play system update. A security update date of 2026-11-01 or later covers CVE-2026-58868 and the other fixes in the Framework, System and Android runtime components. A date of 2026-11-05 or later covers everything in the bulletin, including the kernel and the Arm, Imagination Technologies, MediaTek, Unisoc and Qualcomm components. Google uses two dates so phone makers can ship the common fixes sooner, and it encourages them to include everything.


Phones running Android 10 or later may also get some fixes through Google Play system updates, and this month’s list there includes CVE-2026-58876. CVE-2026-58868 is not on that list, so the date to check for it is the Android security update. The bulletin offers no workaround for phones that cannot install the update yet.


What you should do

Install the November update as soon as your phone offers it, and check the patch level afterward rather than assuming it worked. Phone makers and carriers release updates on their own schedules, so there may be a wait, and owners of older or unsupported phones may never receive the fix, which is a good reason to replace a device that has stopped getting updates. In the meantime, keep Google Play system updates current and be cautious with unexpected messages and unknown apps.


Final thoughts

Zero-click bugs are the ones that worry security teams most, because no amount of user caution can prevent them. The only reliable defense is a fast, steady patching routine, and with Android that depends on how quickly your phone’s manufacturer and carrier deliver updates.


Reference

 
 
 

Comments


Address: Office B322, Level 3, Spaces, Platinum Sentral, KL Sentral, 50470 Kuala Lumpur.

  • Facebook
  • Instagram
  • LinkedIn

Hotline: +60327224705

© 2025 Vardaan Sdn Bhd. All Rights Reserved.

bottom of page