If you’re running Android 12 or 13, a single text message can now crash your phone, and Google has no patch coming. A security researcher has published a working exploit for a flaw called “SMS of Death” that cuts cellular service with one crafted message, no clicks required. For anyone still on those two Android versions, that’s not a theoretical risk anymore. It’s a public tool.
Google fixed the underlying bug, tracked as CVE-2026-58882, in the October 2026 security updates for Android 14 through 17. Researcher Mark Blah found that Android 12 and 13 never got the fix. Oddly, the flaw doesn’t even appear in Google’s October security bulletin, despite the patch showing up in Android’s telephony code.
The bug lives in a function called WapPushOverSms.decodeWapPdu. An attacker sends a malformed eight-byte WAP Push message as a data SMS to port 2948. Android reads a header-length value without checking it first, and that value turns into -2147483648 when interpreted as a signed 32-bit integer. The phone then tries to allocate memory using that negative number, which throws an exception and kills the com.android.phone process. Since that process handles cellular functions, the crash can drop active calls, including calls to emergency services. Blah’s testing found that 20 malicious messages pushed phones into reboot loops, and one Android 12 device kept restarting into recovery mode roughly every 90 seconds until a factory reset fixed it.
This isn’t just another bug report. Blah has released a proof-of-concept exploit that sends these messages from another Android device, which means the attack no longer needs custom tools or deep technical skill. That lowers the bar significantly. Combine that with the fact that millions of phones are still running Android 12 and 13, and you have a real window of exposure with no official fix in sight.
The zero-click part makes this worse. Android processes the malicious message before it ever reaches the inbox, so the person getting attacked sees nothing. No weird text, no warning, just a sudden crash and lost service. A GitHub contributor named Sakis found a way to clear the messages using Android Debug Bridge, but that requires a computer and enough know-how to use ADB, which rules out most regular users. For now, the people most exposed are the ones least equipped to fix it themselves.
Worth Watching
- Will Google backport a fix for Android 12 and 13, or are those versions now effectively abandoned for this issue?
- Why did this fix ship quietly in the telephony code without showing up in the official October bulletin?
- Now that a proof-of-concept exists for sending these messages from another phone, how quickly will this show up in real-world attacks?
Source: Ghacks