Skip to content
COR Intelligence
Back to The Patch Wave
The Patch WaveThis weekFound by: people

Android phones: the November update fixes the hidden text crash and three critical no-tap flaws

COR Solutions3 November 2026
4 min read943 words

Google's November 2026 Android update fixes the hidden text that crashes phones and drops calls, plus three critical flaws that need no tap. No attacks reported.

A hand lifts one of four unbranded smartphones with softly glowing screens from a charging stand on a wooden shelf beside a bright office window and plants.

What happened

On 02/11/2026 Google published its November Android security update. It fixes a bug its finder calls "SMS of Death": one hidden text message that crashes the part of the phone that handles calls and signal, dropping live calls, including emergency calls. Google rates it Critical. The researcher says the message never shows up in the inbox, so the person holding the phone sees nothing. The same update fixes three other critical flaws that Google says could let an attacker run their own code on a phone without the user tapping anything.

Does this affect you

Any Android phone your staff use for work whose security update date is before 1 November 2026. Google's fix covers Android 14 to 17. Phones stuck on Android 12 or 13 aren't on the list, and the researcher who found the text crash says they run the same code and get no fix.

What to do

  1. Ask staff to open Settings, tap About phone, then Android version, and check the Android security update date. Install any waiting update. You want 1 November 2026 or later, and 5 November 2026 if it is offered, as Google says that level covers everything in its November bulletin. If it isn't offered yet, check again in a few days, since each phone maker sends it on its own timetable. Samsung's November update lists all four flaws.
  2. Plan to replace any work phone that can't get past Android 13, starting with the ones people rely on for calls.
  3. If a phone keeps losing signal or rebooting for no reason, have your IT person look at it before resetting it. The researcher says a phone stuck in a reboot loop can be recovered by connecting it to a computer, and warns against choosing "wipe data" at the recovery screen.

Is it being attacked?

Not known. Google's bulletin doesn't say any of these are being used in attacks (checked 04/11/2026), and none are on CISA's exploited list. The text crash code has been public since 29/10/2026. The researcher says that in his tests one message caused on and off outages for up to a week, because the network keeps resending it.

Found by

The text crash was found by the researcher who publishes as Mark B, who reported it to Google on 05/05/2026 and says nothing about using Ai. Tag: people. Google's bulletin doesn't name finders for the three critical code flaws.

For developers

  • November 2026 bulletin (02/11/2026): patch levels 2026-11-01 and 2026-11-05. Critical RCE: CVE-2026-58868 (Framework; CVE.org: out-of-bounds write due to a heap buffer overflow in onOutputReceived of FrameDecoder.cpp), CVE-2026-58876 and CVE-2026-58936 (System). Critical DoS: CVE-2026-58882 (System, decodeWapPdu in WapPushOverSms.java; CVE.org: out of bounds read due to an integer overflow). All listed for AOSP 14, 15, 16, 16-qpr2 and 17. Google says AOSP source patches follow within 48 hours.
  • Google: "Security patch levels of 2026-11-05 or later address all issues associated with the 2026-11-05 security patch level and all previous patch levels." The 2026-11-05 level adds chip-maker fixes, including a Critical Qualcomm closed-source component flaw (CVE-2026-25285). The 2026-11-01 level also carries a second Critical System DoS, CVE-2026-58814.
  • Text crash detail (researcher): WapPushOverSms.decodeWapPdu() casts the WSP header length to int with no range check; a crafted WAP Push data SMS (port 2948) throws NegativeArraySizeException on the telephony main thread and kills com.android.phone. Each message causes 1 to 2 seconds without service while the process restarts; carrier redelivery repeats it, and the queued message is retried on every boot, which can leave the phone in a reboot loop. Around 20 messages can leave a device unusable for an extended period. Proof of concept: github.com/MarkBlah/smsofdeath.
  • Recovery (researcher, credited to @sakisdog): the poison messages sit in content://sms/raw; deleting those rows over ADB just after boot breaks the loop without a factory reset. The full commands are on smsofdeath.com.
  • Versions (researcher): crash reproduced from Android 12 to Android 16; he says Android 12 and 13 run the same code and receive no fix.
  • Fix commit: AOSP 735d967, "RESTRICT AUTOMERGE: Fix remote DoS in decodeWapPdu (b/517376969)", authored 15/06/2026 (US Pacific time), committed 05/08/2026. Its bug number 517376969 matches the bulletin's reference A-517376969 for CVE-2026-58882, which is why this story treats the fix as November's. The researcher says it shipped in October 2026; Google lists the CVE in its November bulletin. Treat 2026-11-01 as the safe patch level.
  • Samsung SMR-NOV-2026 (a maintenance release for major flagship models) lists CVE-2026-58868, CVE-2026-58876, CVE-2026-58882 and CVE-2026-58936 as Critical.
  • Not on CISA KEV (catalogue 2026.11.03, checked 04/11/2026). No exploitation note in the bulletin.

Sources

Read next

More from The Patch Wave