Google Patches Zero-Click Pixel Modem Flaw Under Attack
By @sharedot · · 8 pages
- Cybersecurity
- Google Pixel
- Zero Day
- Zero Click
- Cve 2026 58704
Google fixed CVE-2026-58704, a zero-click Pixel modem privilege-escalation flaw exploited in limited targeted attacks, and CISA set a Sept 19 patch deadline.
What happened
On September 15, 2026, Google released a Pixel security update fixing CVE-2026-58704, a privilege escalation vulnerability in the cellular modem.
The company's bulletin states there are "indications that CVE-2026-58704 may be under limited, targeted exploitation," meaning it was already being used in real attacks before a patch existed — the definition of a zero-day.
The fix ships in security patch level 2026-09-05 and applies to all Pixel models still supported by Google.
Why zero-click is so dangerous
The flaw required no user interaction at all: no link clicking, no file opening, nothing.
According to Korben, an attacker positioned near the target — or on the same network — could exploit a logic error in the modem's code to escape its isolated sandbox and climb to the rest of the phone's data, with the hack remaining invisible to the owner.
Pasquale Pillitteri notes the bulletin calls this "remote (proximal/adjacent)", so the attack does not work from anywhere in the world, but for anyone physically or network-wise close to the victim, the phone gives no warning whatsoever.
The modem: a blind spot defenses don't cover
The modem is the component that talks to the cellular network, handling calls and mobile data on its own firmware, separate from Android. A bug there opens a door that app permissions do not guard.
Pasquale Pillitteri, citing TechRepublic, reports that with the main operating system now far better defended, low-level modem firmware has become a fresh attack vector.
Notably, the flaw is a logic error, so hardware defenses like the Memory Tagging Extension would not have stopped it — a reminder that no single defense covers everything.
The evidence: CISA's three-day deadline
CISA added CVE-2026-58704 to its Known Exploited Vulnerabilities catalog on September 16 and gave US federal civilian agencies until September 19 — just three days — to apply the fix.
Pasquale Pillitteri points out the methodological signal: Google wrote "may be under" exploitation, but the KEV catalog only lists flaws with evidence of active exploitation, so confirmation is effectively there to be read.
The vulnerability is rated high severity with a CVSS score of 8.0, described as a possible permissions bypass from a logic error requiring no privileges.
Who did it, and who else got hit
Google did not attribute the attacks to any actor, and no one has been publicly named. Korben, drawing on TechCrunch, reports that "limited and targeted" is the standard phrasing when commercial spyware sold to governments is suspected — tools used against journalists and opponents.
Per Pasquale Pillitteri, The Hacker News counts 46 critical-severity flaws among the 110 fixes in the September bulletin, affecting components like the bootloader and trusted execution environment.
Korben adds that the timing is awkward for Google, which has long marketed its end-to-end control of Pixel hardware and software as a security advantage.
What Pixel owners should do now
Check the security patch level today: open Settings > Security & privacy > System & updates > Security update, install the September 2026 update, restart, and verify the Android security patch level reads 2026-09-05 or later.
Pasquale Pillitteri stresses that zero-click attacks leave nothing to detect and Google has published no indicators of compromise, so updating — not hunting for traces — is the practical defense.
Pixels that no longer receive patches will not get the fix and stay exposed, and GrapheneOS users should confirm their build includes the September fix through its separate update channel.