Executive Summary
Google has patched CVE-2026-58704, an improper authorization vulnerability in the cellular modem component of Pixel devices. Per the CVE record, a logic error in the modem's permission-checking code creates a possible permission bypass, allowing "remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed." Critically, user interaction is not needed for exploitation — this is a zero-click flaw. Google's September 15, 2026 Pixel Update Bulletin states there are "indications that CVE-2026-58704 may be under limited, targeted exploitation," and the vulnerability was added to CISA's Known Exploited Vulnerabilities (KEV) catalog the following day, confirming that this is a live, in-the-wild attack, not a theoretical disclosure.
CVSS Score: 8.0 (High)
The fix ships as part of the September 2026 Pixel security update, which brings supported devices to security patch level 2026-09-05.
Vulnerability Overview
| Attribute | Value |
|---|---|
| CVE ID | CVE-2026-58704 |
| CVSS Score | 8.0 (High) |
| CWE | CWE-693: Protection Mechanism Failure / Improper Authorization |
| Type | Permission bypass → local/proximal privilege escalation |
| Component | Cellular Modem |
| Attack Vector | Remote (proximal/adjacent) |
| Privileges Required | None (no additional execution privileges needed) |
| User Interaction | None — zero-click |
| KEV Status | Added to CISA KEV September 16, 2026 |
| KEV Due Date | September 19, 2026 |
Affected Versions / Devices
| Product | Affected Component | Fixed Patch Level |
|---|---|---|
| Google Pixel devices (Pixel 6 series through Pixel 11 series, Pixel Tablet, Pixel Fold) | Cellular modem firmware | 2026-09-05 or later |
Google's Pixel Update Bulletin for September 2026 addressed 110 vulnerabilities in total, including this actively exploited flaw and several unrelated critical remote-code-execution issues (in the IP Multimedia Subsystem, the VPU, and elsewhere in the modem stack). The underlying Android bug report for CVE-2026-58704 (tracked internally as A-484011314) remains private, which is standard practice for Google when a fix ships as a binary driver update rather than open-source platform code — but it also means independent researchers cannot yet review the root cause directly.
Devices outside the Pixel 6–11 lineage, or any device not running Google's Pixel-specific modem firmware, are not covered by this advisory.
Attack Vector
The cellular modem on Pixel devices runs on separate, dedicated hardware with its own firmware, operating outside the Android permission model, SELinux, and Play Protect. That isolation is normally a security boundary — a compromised app can't reach the modem's baseband directly — but it also means a bug inside the modem's own authorization logic bypasses all of those Android-side protections at once.
1. An attacker positioned to communicate with the target device's modem
(proximal/adjacent — e.g. over the air interface or a similarly
positioned channel) sends input that reaches the modem's permission-
checking code path
2. A logic error in that code fails to correctly enforce the permission
check that should gate the requested action
3. No additional privileges and no user interaction are required — the
victim does not need to answer a call, open a message, or tap
anything
4. The attacker escalates privileges beyond the modem's intended
sandbox boundary, gaining access to functionality or data that
should have been gated behind proper authorizationBecause exploitation happens at the modem/baseband layer, it leaves few — if any — traces in the logs and detection surfaces (Android system logs, EDR, Play Protect) that defenders normally rely on.
This Is Confirmed, Not Theoretical
Unlike a routine patch-Tuesday-style disclosure, CVE-2026-58704's addition to the CISA KEV catalog means active exploitation has been observed, not merely assessed as likely. Google itself flagged "limited, targeted exploitation" in its own advisory — language the company has historically reserved for exploitation patterns associated with narrowly targeted surveillance operations rather than broad, opportunistic campaigns. Google has not attributed the activity to a specific threat actor, and there is no public proof-of-concept exploit code at the time of writing.
Why This Matters
Modem-level privilege escalation bugs are unusually valuable to sophisticated attackers for a specific reason: they can operate beneath the Android security model entirely. A flaw here doesn't need to trick a user, abuse an installed app, or survive Play Protect scanning — it targets a privileged subsystem that most on-device defenses were never designed to monitor. Historically, this class of bug (modem/baseband logic errors, zero-click, no user interaction) has been the kind of vulnerability chained by commercial spyware vendors and state-aligned surveillance operators to compromise specific, high-value individuals rather than the general public. Google has not confirmed that attribution here, and readers should treat any such framing as informed context, not a confirmed finding.
The "limited, targeted" scope also means most Pixel owners were not individually targeted — but the fix should still be applied promptly, because the same underlying flaw becomes far more dangerous once technical details or working exploit code become public.
Remediation
Step 1: Confirm and Install the September 2026 Security Update
- Open Settings
- Navigate to Security & privacy → System & updates
- Tap Security update
- Select Install if an update is available, then restart the device
Step 2: Verify the Patch Level
After updating, confirm the device reports security patch level 2026-09-05 or later (visible under Settings → About phone → Android version).
Step 3: For Fleet / MDM-Managed Devices
- Push the September 2026 security update through your mobile device management platform without delay — this is a KEV-listed, zero-click, no-privileges-required flaw
- Prioritize devices most likely to be high-value targets (executives, legal, security, and policy personnel) given the "limited, targeted" exploitation pattern
- Federal civilian agencies should track this against CISA's KEV catalog remediation due date of September 19, 2026
There is no user-facing workaround for this vulnerability short of installing the fix; it lives in modem firmware, not an app or setting that can be individually disabled.
References
- CISA Known Exploited Vulnerabilities Catalog — Google Pixel Improper Authorization Vulnerability (CVE-2026-58704)
- NIST NVD — CVE-2026-58704
- Google — Pixel Update Bulletin, September 2026
- SecurityWeek — Pixel Modem Zero-Day Exploited in Targeted Attacks