CyberHunter

Android November 2026 bulletin: 216 flaws, three zero-click RCEs, and the "SMS of Death" listed as critical

Google's November bulletin fixes 216 CVEs, 23 of them critical, including three zero-click remote code execution bugs. The "SMS of Death" (CVE-2026-58882) is listed; Android 12 and 13 stay exposed.

Share LinkedIn X Download video (MP4)

What happened

Google published the Android Security Bulletin for November 2026 on 2 November. It covers 216 vulnerabilities, 23 of them rated Critical. The headline issues are three remote code execution flaws that need no user interaction. The bulletin also officially lists the "SMS of Death" (CVE-2026-58882), a remote crash triggered by one invisible text message, rated Critical.

Google does not flag any issue as exploited in the wild this month.

The fixes ship at two patch levels:

  • 2026-11-01: Android itself (runtime, Framework, System, Google Play system updates), 119 CVEs.
  • 2026-11-05: the kernel and chip vendors (Arm, Imagination, MediaTek, Unisoc, Qualcomm), 97 CVEs.

Only a device showing 2026-11-05 or later has every fix.

The three zero-click RCEs

CVE Component Android versions
CVE-2026-58868 Framework 14, 15, 16, 16 QPR2, 17
CVE-2026-58876 System 14, 15, 16, 16 QPR2, 17
CVE-2026-58936 System 14, 15, 16, 16 QPR2, 17

Google sums up the worst one in a single sentence: a critical flaw in the Framework component that "could lead to remote code execution with no additional execution privileges needed", and user interaction "is not needed for exploitation". The System section carries the same warning.

Google does not publish technical details before the source patches reach AOSP. The bulletin says that should happen within 48 hours. We do not know yet which input reaches these bugs (a message, a media file, a network packet).

The other critical flaws

  • Privilege escalation in System: CVE-2026-55275, CVE-2026-55283 and CVE-2026-58984.
  • Denial of service in System: CVE-2026-58814, plus the SMS of Death.
  • Kernel: five privilege escalations, in Bluetooth (CVE-2026-53256, CVE-2026-89774), pKVM (CVE-2026-59044, CVE-2026-59045) and HID (CVE-2026-80604), plus one information leak in pKVM (CVE-2026-59048).
  • MediaTek modem: eight critical flaws, CVE-2026-20499, 20519, 20520 and 20545 to 20549. The modem processes radio traffic before Android sees it.
  • Qualcomm: one critical flaw in a closed-source component, CVE-2026-25285.

SMS of Death: one invisible SMS, no more calls

CVE-2026-58882 was found by an independent researcher who publishes as Mark B (MarkBlah on GitHub). He reported it to Google on 5 May 2026, published the details and a proof of concept on 29 October, and the bulletin lists it as Critical (denial of service).

How it works. The attacker sends a data SMS carrying a WAP Push message to port 2948. That is the channel Android uses for MMS notifications and network settings. The WapPushOverSms code reads a header length from the message without checking its range:

  1. A crafted value, 0x80000000, becomes a negative number once converted.
  2. Android tries to allocate an array of that size and throws an exception nobody catches.
  3. The com.android.phone process, which handles calls, SMS and mobile data, crashes.

The message is processed before it reaches the inbox, so the user sees nothing, not even the sender.

The effects:

  • every message cuts service for one to two seconds;
  • active calls are dropped, emergency calls included;
  • the message stays in the pending queue and is retried on every reboot, so the phone can crash during startup and fall into a reboot loop that ends on a "wipe data" prompt;
  • according to the researcher, one message can cause intermittent outages for up to a week, and about twenty can make a phone unusable.

The researcher reproduced it on a Pixel 9 and on several Samsung Galaxy models.

The fix. Google catches the error and deletes the faulty message from the queue. According to the researcher, the code fix was already in the October 2026 release for Android 14 to 17. The November bulletin is where the CVE is officially listed. A phone at patch level 2026-10-01 or later is protected.

Android 12 and 13 stay exposed

The vulnerable code has existed since Android 12, but Google's fixes only cover Android 14, 15, 16 and 17, the versions still inside the security update window. The November bulletin does not mention Android 12, 12L or 13 at all.

The researcher states that these versions "run the same code and do not receive the fix". Many phones still in use are affected, especially entry-level models and devices whose manufacturer has stopped updating them. For them the SMS of Death stays usable, with a public proof of concept.

What to do

  1. Check your patch level: Settings > About phone > Android version > Android security update. Aim for 5 November 2026. If you see 1 November, the kernel and chip fixes (MediaTek, Qualcomm) are missing.
  2. Install the update as soon as your manufacturer releases it. Pixels usually get it first. Samsung, Xiaomi and others follow on their own schedule.
  3. On Android 12 or 13:
    • there is no fix for the SMS of Death, and the three zero-click RCEs do not list those versions;
    • check whether your manufacturer offers an upgrade to Android 14 or later;
    • otherwise plan to replace the phone, especially for work or high-exposure use.
  4. Fleet managers: use your MDM to require patch level 2026-11-05 for corporate access, and list the Android 12 and 13 devices still on the network.
  5. If a phone is stuck in a reboot loop after a suspicious SMS, do not choose "wipe data" in recovery. The researcher documents an ADB procedure that deletes the faulty message from the pending queue (content://sms/raw) and keeps the data.

More vulnerability news

All news