Android SMS of Death Zero-Click Text Message Crash Threatens Phones
November 1, 2026
A zero-click Android vulnerability, dubbed the SMS of Death, lets attackers crash phones by sending a single malformed text message. The flaw, tracked as CVE-2026-58882, disrupts cellular service and can even interrupt emergency calls without any user interaction.
What Happened: SMS of Death Attacks Crash Android Phones Worldwide
Security researcher Mark Blaszczyk disclosed a critical Android vulnerability on October 30, 2026. This flaw is a remote, zero-click denial-of-service attack that crashes the com.android.phone process. Consequently, victims lose cellular connectivity and cannot make or receive calls.
The attack is invisible to victims. Moreover, Android processes the malicious message before it ever reaches the SMS inbox, leaving no trace. Carriers also attempt to redeliver unconfirmed messages, which means a single text can cause repeated outages lasting up to a week.
Technical Details of the SMS of Death Vulnerability
The flaw lives in Android’s WapPushOverSms.decodeWapPdu function. An unchecked type cast turns a manipulated length value in the WSP header into a negative array size. This triggers an unhandled NegativeArraySizeException, which immediately crashes the telephony service.
To exploit the flaw, an attacker sends the following malformed eight-byte WAP Push message as a data SMS to port 2948:
01 06 88 80 80 80 00 BE
When this value is translated into a signed 32-bit integer without a bounds check, it becomes -2147483648. Android then tries to allocate memory using this negative value, causing the crash.
Affected Android Versions
- Android 12: No patch expected; out of support
- Android 13: No patch expected; out of support
- Android 14: Patched in October 2026 security update
- Android 15: Patched in October 2026 security update
- Android 16: Patched in October 2026 security update
- Android 17: Patched in October 2026 security update
Business and Operational Impact
The SMS of Death vulnerability poses severe risks to both consumers and enterprises. Furthermore, the potential to disrupt emergency calls raises public safety concerns. Key impacts include:
- Communication Disruption: Active calls drop immediately, and cellular service fails until the device reboots.
- Emergency Call Interruption: Ongoing emergency calls can be severed, delaying critical first-responder contact.
- Device Destruction: Approximately 20 malicious messages can trap phones in reboot loops, rendering them unusable.
- Data Loss Risk: Phones stuck in recovery mode every 90 seconds may force inexperienced users to factory reset, erasing all data.
- Enterprise Mobility Disruption: Organizations with large Android fleets face downtime and support-ticket surges.
Mitigation and Recommendations
Immediate action is essential to protect Android devices from this attack. Therefore, organizations and individuals should apply the following mitigations:
Immediate Actions for Defenders
- Apply Security Updates: Install the October 2026 Android security patch on all supported devices immediately.
- Rotate to Supported Devices: Replace Android 12 and 13 devices with models running Android 14 or newer, since those older versions will not receive patches.
- Enforce MDM Policies: Use mobile device management to mandate patch compliance and quarantine unpatched endpoints.
- Block WAP Push Messages: Contact carriers to disable WAP Push SMS if it is not required for business operations.
- Monitor for Repeated Crashes: Investigate phones that crash repeatedly and attempt ADB-based message removal before wiping data.
Recovery Guidance for Affected Users
If a device enters a reboot loop, do not select Wipe data in recovery mode. Instead, connect the phone to a PC via Android Debug Bridge (ADB) and remove the malicious SMS from the SMS database. However, this process requires technical expertise and a computer.
Bottom line: Android users on versions 12 and 13 face a permanent, unpatched threat. Everyone else must install the October 2026 security update immediately to prevent remote crashes and potential data loss.
Incident Summary
| CVE ID / Incident: | CVE-2026-58882 |
| Affected Systems: | Android 12 through 17 |
| Disclosure Date: | October 30, 2026 |
| Patch Status: | Android 14-17 patched in October 2026; Android 12-13 unpatched |
| Severity: | Critical |
| Attack Vector: | Network (zero-click via malformed WAP Push SMS) |
References
- BleepingComputer, “New Android SMS of Death exploit can remotely crash unpatched phones,” October 31, 2026, https://www.bleepingcomputer.com/news/security/new-android-sms-of-death-exploit-can-remotely-crash-unpatched-phones/, accessed November 1, 2026.
- heise online, “SMS of Death: Security flaw crashes Android phones,” October 30, 2026, https://www.heise.de/en/news/SMS-of-Death-Security-flaw-crashes-Android-phones-11506625.html, accessed November 1, 2026.
- PhoneArena, “A simple text message can instantly ruin your phone,” October 30, 2026, https://www.phonearena.com/news/a-simple-text-message-can-instantly-ruin-your-phone–heres-how-to-stop-it_id184454, accessed November 1, 2026.