news DeafNews

SMS of Death: An 8-Byte Message Crashes Android and Blocks Emergency Calls

CVE-2026-58882 is described as a critical, zero-click denial-of-service vulnerability in Android’s WAP Push SMS processor. An attacker can send an 8-byte malformed data SMS that exploits an integer-conversion error in the `decodeWapPdu` function, causing the `com.android.phone` process to crash. The attack requires no user interaction, produces no notification, and reportedly reproduces reliably on Pixel and Samsung Galaxy devices. A single message can terminate active cellular calls, including emergency calls, for roughly one to two seconds. About 20 repeated messages may trigger Android’s RescueParty system, forcing the device into recovery mode and creating a persistent reboot loop. Recovering without erasing data may require previously enabled Android Debug Bridge access or advanced recovery procedures; less technical users may face a factory reset. Google reportedly implemented a fix in June 2026 and distributed it through the October security update for Android 14 through 17. However, the vulnerability was omitted from Google’s official bulletin, and Android 12 and 13 remain exposed with no confirmed backport or practical mitigation for ordinary users. The flaw was initially classified as a non-security issue after being reported in May, according to the researcher. Because the proof of concept is public, the issue highlights risks from Android’s fragmented patch support and incomplete vulnerability disclosure. Users should install the October 2026 update or later where available, while administrators must verify exact OS versions rather than relying solely on generic patch-level information.

Build this article’s timeline

Extract dated events, key actors, and open questions using the same timeline analysis available in Signal.

Log in to build

Timeline generation is available to signed-in community members.

Five Ws 🤖 3 AI prefills · 2 still unanswered
Who
Mark Blah, Mark Blaszczyk, Sakis, and Google
🤖 AI prefill
What
CVE-2026-58882 is described as a critical, zero-click denial-of-service vulnerability in Android’s WAP Push SMS processor.
🤖 AI prefill
When When did this happen, or what is the timeframe?
Where Where did this occur?
Why
Centers on CVE-2026-58882, zero-click WAP Push SMS vulnerability, and Android patching fragmentation
🤖 AI prefill

Login to answer and earn XP for each gap you fill.

Android WAP Vulnerability CVE-2026-58882, WAP Push, SMS, zero-click, parser Crash And Bootloop Impact denial of service, emergency calls, cellular connectivity, reboot loop, RescueParty Android Patch Fragmentation Android 14, Android 15, Android 16, Android 17, Android 12 Disclosure And Governance Google, security bulletin, coordinated disclosure, non-security issue, proof of concept Mitigation And Recovery Android Debug Bridge, ADB, USB debugging, developer options, SMS database
CVE-2026-58882100% zero-click WAP Push SMS vulnerability98% Android patching fragmentation95% com.android.phone process crash94% persistent reboot loop92% emergency call disruption91% WAP Push parser90% long-to-int integer overflow89% NegativeArraySizeException87% Android RescueParty85%
42
Manipulation Score: Medium How much this article uses emotional framing vs. straight reporting
Loaded Language 3825%
Absolutist 3415%
Threat/Panic 5825%
Us vs Them 1815%
Engagement Bait 2220%
Manipulation score look right?

Factual Claims (10)

high technology
CVE-2026-58882 allegedly lets a remote attacker crash Android phones with an 8-byte WAP Push SMS.
high technology
The vulnerability can interrupt active calls, including emergency calls, and may cause persistent reboot loops.
medium technology
Google fixed the vulnerability in the October 2026 security update for Android 14, 15, 16, and 17.
high technology
Android 12 and 13 do not receive the patch and remain exposed.
high technology
The flaw is described as a zero-click vulnerability in Android's WAP Push parser.
high technology
Roughly 20 malformed messages can trigger a continuous reboot cycle into recovery mode.
medium technology
Google initially classified the May 5, 2026 report as a non-security issue.
high technology
The public proof of concept uses an integer-conversion error that produces a NegativeArraySizeException.
high technology
The researcher reported a 100% reproduction rate on Google Pixel and Samsung Galaxy devices.
medium technology
Google omitted CVE-2026-58882 from the October 2026 official security bulletin.

Comments

Login to view and post comments.

🏠Portal 📰Links ❓Q&A 📅Events 💼Jobs