Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2026-58704: Permission Bypass and Privilege Escalation in Google Pixel Cellular Modem

Published Sep 15, 2026 · Updated 14 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.63%51st percentile
CISA KEVYesAdded Sep 16, 2026
In the wildActivePer CISA KEV
Vendor
Google
IdentifiersCVE-2026-58704CWE-285 · Improper Authorization

CVE-2026-58704 is a high-severity improper authorization vulnerability in the Google Pixel Cellular Modem component. A logic error allows an intended permission check to be bypassed, potentially enabling remote privilege escalation from a proximal or adjacent attack position without user interaction. The specific vulnerable function and triggering input have not been publicly disclosed. Google reported indications of limited, targeted exploitation and fixed the vulnerability in the September 2026 Pixel security update. CISA added it to the Known Exploited Vulnerabilities catalog on September 16, 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation bypasses modem permission checks and enables unauthorized privilege escalation on an affected Pixel device, potentially compromising device functions and data. The reported CVSS assessment assigns high confidentiality, integrity, and availability impacts. The exact privileges obtained, extent of access beyond the modem, and observed post-exploitation actions have not been publicly established.

Mitigation

If you can’t patch tonight, do this now.

No validated alternative workaround has been disclosed. Until updates are deployed, inventory affected Pixel devices, prioritize devices used by high-risk personnel, and restrict sensitive enterprise access from unpatched or noncompliant devices. Enforce the minimum fixed patch level through device-management policy. Conventional Android security agents may have limited visibility into modem exploitation; suspected compromise warrants incident-response assessment even after patching.

Remediation

Patch, then assume compromise.

Install the September 2026 Pixel security update or a subsequent applicable vendor update, and verify that the device reports security patch level 2026-09-05 or later. Restart if prompted to complete installation. Ensure that the update includes Pixel-specific modem firmware fixes; generic Android patches or an alternative operating system alone do not establish that the vulnerable modem component has been updated.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system
FAQ

Frequently asked questions

Is CVE-2026-58704 exploited in the wild?
Yes. As of Nov 3, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 16, 2026.
Is there a public exploit for CVE-2026-58704?
As of Nov 3, 2026, Mallory has found no public exploit for CVE-2026-58704.
Is there a patch for CVE-2026-58704?
Install the September 2026 Pixel security update or a subsequent applicable vendor update, and verify that the device reports security patch level 2026-09-05 or later. Restart if prompted to complete installation.
What products are affected by CVE-2026-58704?
Google Android.
How severe is CVE-2026-58704?
CVE-2026-58704 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.63% (51st percentile) as of Nov 3, 2026.
Activity feed

Recent activity

131 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
the hacker newsNews · Oct 9, 2026Three Teams Demonstrate Remote Hacks of Fully Patched Google Pixel 10 at Pwn2OwnA modem vulnerability affecting Google Pixel phones, mentioned as background separate from the Pwn2Own exploits. Google warned of possible limited, targeted exploitation and released a fix in September 2026. The content does not describe the technical cause or impact.Read more ↗kaspersky blogNews · Oct 2, 2026110 vulnerabilities fixed in Google Pixel devices | Kaspersky official blogAn actively exploited zero-day elevation-of-privilege vulnerability in Google Pixel cellular modem software. Exploitation requires pre-existing low-level privileges on the device and occurs through the cellular network, potentially involving a compromised network or malicious cellular base station.Read more ↗kaspersky ruNews · Sep 30, 2026Как закрыть 110 уязвимостей в Google Pixel | Блог КасперскогоA Google Pixel cellular-modem zero-day logic flaw that allows an attacker with initial/basic privileges on the device to elevate privileges. Exploitation occurs through the cellular network and may require compromise of the victim's existing cellular network or coercing the device to connect to an attacker-controlled malicious base station.Read more ↗xakepNews · Sep 18, 2026Google патчит 0-day-уязвимость в устройствах Pixel - ХакерA CVSS 8.0 logical-error vulnerability in the Pixel cellular modem that bypasses permission checks and enables remote, zero-click privilege escalation without user interaction.Read more ↗
+20 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity103Community discussion across Reddit, Mastodon, and other social sources.