Google has released an emergency security update as part of its September 2026 patch cycle for Pixel devices, addressing a total of 110 vulnerabilities. Among them is a high-severity zero-day flaw, CVE-2026-58704, which affects the cellular modem component. The vulnerability is a privilege escalation issue with a CVSS score of 8.0. Google has confirmed there are indications that this flaw is under "limited, targeted exploitation" in the wild. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added it to its Known Exploited Vulnerabilities (KEV) catalog, underscoring the urgency for users to update their devices.
CVE-2026-58704 is a privilege escalation vulnerability rooted in a logic error within the Pixel's modem code. This flaw allows an attacker to bypass permission checks. The attack vector is described as "proximal/adjacent," meaning the attacker would likely need to be physically near the target device to interact with the cellular modem's radio interface. Crucially, the exploit requires no user interaction, such as clicking a malicious link or installing an app. A successful exploit could allow an attacker to gain elevated privileges on the device, potentially leading to further compromise.
The vulnerability affects Google Pixel devices. While specific models were not detailed in the source articles, the patch is included in the September 2026 security update for all supported Pixel phones. Users should apply the security patch level of 2026-09-05 or later.
Google's advisory explicitly states that CVE-2026-58704 may be under limited, targeted exploitation. The company has not provided details on the nature of these attacks, the threat actors involved, or the targets. On September 16, 2026, CISA added the vulnerability to its KEV catalog, mandating that U.S. Federal Civilian Executive Branch agencies patch their devices by September 19, 2026.
A privilege escalation vulnerability within a device's modem (baseband processor) is significant. The modem operates as a separate, complex computer within the phone, with its own operating system and direct access to cellular communications. An attacker with elevated privileges in this environment could potentially:
The lack of required user interaction makes this flaw particularly dangerous for high-value targets.
Direct detection of modem-level exploitation is extremely difficult for end-users and most security tools. The following are indirect methods for identifying vulnerable systems:
2026-09-05 on Pixel devices.getprop ro.build.version.security_patchDetection of exploitation is not feasible for most organizations. The focus must be on prevention and inventory management.
2026-09-05 security patch level or later. This can be achieved through D3FEND Software Update (D3-SU) status checks.Settings > Security & privacy > System & updates > Security update.Applying the vendor-supplied security update is the only effective way to remediate this vulnerability.
While direct detection is hard, advanced endpoint security may detect anomalous behavior resulting from post-exploitation activity.
Google releases September 2026 security update patching CVE-2026-58704.
CISA adds CVE-2026-58704 to its Known Exploited Vulnerabilities (KEV) catalog.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.