Google Fixes Exploited Pixel Modem Flaw CVE-2026-58704

Google Patches Actively Exploited Zero-Day Flaw in Pixel Modems

HIGH
September 16, 2026
4m read
VulnerabilityMobile SecurityPatch Management

Related Entities

CVE Identifiers

CVE-2026-58704
HIGH
CVSS:8

Full Report

Executive Summary

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.

Vulnerability Details

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.

Affected Systems

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.

Exploitation Status

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.

Impact Assessment

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:

  • Intercept or manipulate cellular data and voice calls.
  • Gain a persistent foothold on the device that is difficult to detect and remove.
  • Pivot from the compromised modem to the main application processor, potentially leading to a full device takeover.

The lack of required user interaction makes this flaw particularly dangerous for high-value targets.

Cyber Observables — Hunting Hints

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:

Type
Other
Value
Android Security Patch Level
Description
Check for a patch level earlier than 2026-09-05 on Pixel devices.
Type
Command Line Pattern
Value
getprop ro.build.version.security_patch
Description
On-device command (via ADB) to check the current security patch level.
Type
Log Source
Value
Mobile Device Management (MDM) logs
Description
MDM solutions can query and report on the patch status of enrolled devices, identifying vulnerable assets.

Detection Methods

Detection of exploitation is not feasible for most organizations. The focus must be on prevention and inventory management.

  1. Asset Management: Use a Mobile Device Management (MDM) or Unified Endpoint Management (UEM) platform to inventory all Pixel devices within the organization.
  2. Version Scanning: Query all managed Pixel devices to identify those that have not yet been updated to the 2026-09-05 security patch level or later. This can be achieved through D3FEND Software Update (D3-SU) status checks.
  3. Compliance Reporting: Generate compliance reports to track the patching progress and enforce policies requiring users to update their devices.

Remediation Steps

  1. Apply Security Update: The only effective remediation is to install the September 2026 security update from Google. Pixel users can check for the update by navigating to Settings > Security & privacy > System & updates > Security update.
  2. Enforce Patching Policies: Organizations should use their MDM/UEM solution to enforce the installation of the update on corporate-managed devices.
  3. User Communication: Inform users about the critical nature of this update and provide clear instructions on how to install it on both personal (BYOD) and corporate devices.

Timeline of Events

1
September 16, 2026
Google releases September 2026 security update patching CVE-2026-58704.
2
September 16, 2026
CISA adds CVE-2026-58704 to its Known Exploited Vulnerabilities (KEV) catalog.
3
September 16, 2026
This article was published

MITRE ATT&CK Mitigations

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.

Timeline of Events

1
September 16, 2026

Google releases September 2026 security update patching CVE-2026-58704.

2
September 16, 2026

CISA adds CVE-2026-58704 to its Known Exploited Vulnerabilities (KEV) catalog.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

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.

Tags

Zero-DayPrivilege EscalationMobile SecurityAndroidKEVGooglePixel

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.