Skip to content
major vulnerability· requires attention

Actively exploited CISA KEV issue affecting widely used Google Pixel devices' cellular modem allowing remote privilege escalation without user interaction.

Mobile

CVE-2026-58704

8.8
High
KEV · Exploited in wildEPSS n/aPatch availableSep 17, 2026

Modem auth bypass on Pixel enables remote privilege escalation

common questions

Is CVE-2026-58704 being exploited?

Yes. CVE-2026-58704 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-58704?

CVE-2026-58704 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-58704?

Yes. A fix has been recorded for CVE-2026-58704. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58704 affect?

CVE-2026-58704 affects Google Pixel devices, Android (cellular modem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58704?

Install Pixel security update now; apply vendor and CISA mitigations

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Pixel devicesAndroid (cellular modem)
impact

Adjacent attacker bypasses modem authorization to escalate privileges on Pixel devices without user interaction, enabling persistent compromise and data access.

action required

Immediate action required

affected versions
Google Android
  • affectedAndroid kernel

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free