One hidden text can knock an Android phone offline
Android 'SMS of Death' exploit released: one text can crash phones or drop calls, no tap needed
The flaw sits in how Android handles a special type of text message. It is rated Critical in Google's November bulletin. In the researcher's tests, repeated messages left phones rebooting in a loop, and one needed a factory reset. Reports differ on whether the fix arrived in October or November, and no source says it has been used against real victims.
What to do this week
- Check the security update date on each Android phone.Open Settings, then About phone, then Android version, and look for "Android security update". The wording varies by brand. You want 2026-11-01 or later.
- Install any update that's waiting.Go to Settings, then System, then Software update. Restart if asked. If the date is still old and nothing is offered, your phone maker or carrier hasn't released it yet. Check again in a few days.
- Look at your parents' phones, not just your own.If it runs Android 12 or 13, or no longer gets security updates, assume it stays exposed. Plan a replacement, and treat it as a priority, not a someday job.
- Make sure there's a second way to call for help.If a phone keeps crashing or losing service, a landline, a second phone or a medical alert pendant covers the gap.
- If a phone starts crashing or restarting repeatedly, don't just wipe it.Contact the phone maker or your carrier, or ask someone technical to help. The researcher published a way to remove the bad messages from a computer without a factory reset, but it needs technical skill, so we're not linking it.
Or have someone do it. Keeping every family phone current, and knowing which ones can no longer be updated, is exactly what private cybersecurity is for.
What happened
On 31 October, a security researcher published working exploit code for an Android flaw nicknamed "SMS of Death". Send the right text to a vulnerable phone and its calling system crashes. The owner doesn't have to open the message, tap a link or even see a notification.
The bug is tracked as CVE-2026-58882. According to BleepingComputer[1], the message is handled by Android before it reaches the text inbox, so the victim has no sign of what is happening. The result can be dropped calls, lost mobile service or a phone that crashes over and over. In the researcher's tests, a batch of about 20 malicious messages trapped phones in reboot loops. One Android 12 phone kept restarting into recovery every 90 seconds or so and needed a factory reset.
Google has patched the flaw for newer versions of Android. The harder part is that many phones haven't received the update yet, and some never will.
- Severity
- High Google rates it Critical in its November bulletin
- What it does
- Crashes the phone's calling system; can drop calls, cut mobile service or cause reboot loops
- What the victim does
- Nothing. No tap or open needed
- Fixed in
- Android security patch level 2026-11-01 or later, per Google's bulletin
- Phones with a fix
- Android 14, 15, 16 and 17, once the update reaches them
- Phones without one
- Android 12 and 13, per BleepingComputer; Google's bulletin doesn't list them
- Exploit code
- Public since about 31 October
- Used on real victims
- Not reported
The full story3 more sections
Timeline
Researcher Mark Blaszczyk told Google about the flaw on 5 May, according to eSecurityPlanet[3], which says a fix was written by 15 June. The exploit code appeared around 31 October. Google's bulletin, published on 2 November, lists the flaw as Critical.
Where the reports disagree
BleepingComputer says Google fixed this in its October 2026 updates for Android 14 to 17, and that the flaw wasn't named in the October bulletin. Google's own November bulletin does list it, under the 2026-11-01 patch level. eSecurityPlanet says GrapheneOS pointed to the November bulletin for the fix.
For a family, the practical answer is the same. A phone showing a security update date of 2026-11-01 or later is covered. An earlier date may or may not be.
You can't ignore a text you never see. The only defence is the update.
Who is affected
Anyone on Android, and the people who still use an old one
Every Android phone that hasn't installed the fix is exposed, and the update can lag behind Google's release because phone makers and mobile carriers pass it on in their own time. Phones on Android 12 and 13 are the bigger worry. BleepingComputer says they did not get the fix and remain vulnerable.
That describes the hand-me-down phone a parent or grandparent is still using. iPhones aren't mentioned in any of the reports.
So far this looks like a nuisance and a disruption, not a way to steal data. Nothing reported says it lets an attacker see messages, photos or bank apps. But a phone that keeps dropping out matters if it is someone's only way to ring for help. eSecurityPlanet notes the crash can cut calls, including emergency calls.
The exploit can reportedly send the malicious messages from another Android device, so anyone with the code and a spare phone can try it. No source says it has been used against real victims yet.
Timeline
-
HARD publishes its article, at High.
References4
- ^ BleepingComputer (). “New Android SMS of Death exploit can remotely crash unpatched phones”. Exploit release, impact, reboot loop tests, Android 12/13 not fixed, October update claim.
- ^ Android Open Source Project (Google) (). “Android Security Bulletin: November 2026”. Lists CVE-2026-58882 as Critical DoS, Android 14-17, fixed at patch level 2026-11-01.
- ^ eSecurityPlanet (). “Android 'SMS of Death' Flaw Can Drop Emergency Calls, Trigger Reboot Loops”. Researcher name, 5 May report, 15 June fix, emergency calls, GrapheneOS note, version conflict.
- SmartScope (). “Android SMS Handling Remote Denial of Service (CVE-2026-58882)”. Secondary source: patch level 2026-11-01, no exploitation reported, not on CISA KEV as of 3 Nov.
Situation Room articles are updated as events develop: updates are added to the timeline, and never edited away. Follow them by email or RSS.

