Your Pixel 9 lights up with a message—audio, transcribed automatically. No click needed. Boom. Owned.
That’s the chilling reality of a 0-click exploit chain for the Pixel 9, as laid bare in Project Zero’s latest salvo. These folks at Google—yeah, Google’s own elite bug hunters—spent weeks chaining nasties like the Dolby UDC codec and BigWave driver bugs into a remote takeover. And they’re not mincing words about the mess.
Audio Messages: The Unseen Doorway
Google Messages transcribes incoming audio before you even glance at it. Smart, right? Except on Pixel 9, another process—com.google.android.tts—jumps in to decode that sound too. Why? Searchability, maybe. Who knows.
Both chew through every decoder on the device. Including Dolby UDC, that OEM-favored oddity for movie audio formats nobody’s sending in texts. Seriously—Android lacks encoders for it. Yet there it sits, primed for exploitation.
Project Zero nails it:
The Dolby UDC is part of the 0-click attack surface of most Android devices because of audio transcription in the Google Messages application. Incoming audio messages are transcribed before a user interacts with the message.
Remove these fringe decoders from the auto-play zone, they say. Duh. But AI features? They’re exploding the attack surface. Every “helpful” transcription or search tweak risks pulling in more code for attackers to poke.
Vendors chase features without a security audit. Sloppy. And users pay.
Why Does Pixel 9’s Attack Surface Feel So Sloppy?
Hackathons. One week, and Ivan bags CVE-2025-54957 in Dolby UDC. Less than two days. Seth? One day on BigWave’s CVE-2025-36934.
Prep work mattered—three weeks tooling up. Still, person-weeks total for a full chain. Nation-states laugh at that timeline.
Android fuzzes codecs via OSS-Fuzz. Good on ya. But Pixel skips UDC? Gaps everywhere. Drivers? Softer than butter. GTIG spotted 16 in-the-wild driver bugs since 2023.
Here’s my hot take, absent from the post: This echoes the iPhone’s 2009-2010 era, when SMS and PDF parsers were playgrounds for jailbreaks. Google dismissed those as ancient history—yet here we are, with audio playing the same fool’s role. Without a full 0-click surface map (and fuzzing it relentlessly), Pixels risk weekly chains from Beijing or Moscow.
Drivers: Android’s Eternal Achilles Heel
BigWave. Just one example. Samsung, Qualcomm, ARM—they patch, sure. But attackers lap ‘em.
Rust rewrites? Security reviews? Less privilege? Updatable drivers? All on the table. Yet urgency lags.
Google’s spinning fuzzing wins, but overlooks OEM silos. PR gloss over real gaps. Classic.
Exploitation time? Eight person-weeks for UDC, three for BigWave POC. Peanuts for pros.
AI Boom, Security Bust?
AI everywhere—transcribe this, search that. Noble. But each feature bloats the unclicked code.
Deliberate reviews? Ha. Software creeps, surfaces swell.
Prediction: By 2026, half of 0-clicks hit via AI hooks. Unless OEMs audit ruthlessly.
Pixels promise top security. Reality? Overlooked codecs beg to differ.
The Fix-It Wishlist
Rigorous attack surface audits. Fuzz everything—UDC included. Strip unused decoders from Messages.
Drivers: Mandate Rust for new ones. Cage ‘em from userland. Auto-updates, stat.
OEMs, wake up. Your Dolby toys aren’t for texts.
Short version? Android’s coasting. Attackers sprint.
And that’s before quantum or next-gen AI vectors.
🧬 Related Insights
- Read more:
- Read more: 14,000 F5 BIG-IP Doors Wide Open to RCE Nightmares
Frequently Asked Questions
What causes 0-click exploits on Pixel 9?
Audio transcription in Google Messages auto-decodes files with obscure codecs like Dolby UDC, letting attackers chain bugs remotely—no user action needed.
How long to exploit Pixel 9 vulnerabilities like CVE-2025-54957?
Project Zero clocked person-weeks: eight for the codec, three for the driver POC. Pros do it faster.
Will Google remove Dolby UDC from Pixels?
Unclear—recommendations push stripping it from 0-click paths, but OEM integrations and features complicate it. Patch and audit first.
