CVE-2026-58704: Google Pixel Improper Authorization
Google Pixel · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-16.
- CVSS v3.1 (CISA ADP)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 0.6%
- higher than 50.8% of all CVEs
- Added to CISA KEV
- 2026-09-16
- US federal due date 2026-09-19
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-58704 explained
CVE-2026-58704 is an improper authorization flaw in the Cellular Modem component of Google Pixel devices. A logic error allows a permission bypass that can lead to escalation of privilege from an adjacent position without user interaction. CISA lists it as known to be exploited, so affected devices should be prioritized.
Impact
An attacker within proximal or adjacent network range can escalate privileges without credentials, additional execution privileges or user interaction. Successful exploitation can fully compromise confidentiality, integrity and availability of the affected component. CISA rates the technical impact as total, meaning full control of the component. CISA judges it not automatable, so mass exploitation without manual steps is less likely. Attackers are known to exploit it.
Who is affected
The CVE record (CNA: Google_Devices) describes affected versions in free text. It lists Google Android, with "Android kernel" as the affected item, in the context of the Pixel Cellular Modem. The CVE record names no fixed version. Check the vendor advisory to find which Pixel security update addresses the issue.
Written with AI from the data on this page and checked against it automatically.
Official description
In Cellular Modem, there is a possible permission bypass due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Google AndroidAffectedFixed in
- Android kernel
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| Google AndroidVersion statement as published by the CNA (free text). |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: source.android.com/docs/security/bulletin/pixel/2026/2026…
- CISA's deadline for US federal agencies: 2026-09-19 (passed) – a useful benchmark for everyone else, too.
What to do
- Check the Google vendor advisory to identify the Pixel security update that addresses CVE-2026-58704.
- Install the latest available security update on all managed Pixel devices.
- Use device management tools to confirm the update reached every device and flag devices that cannot update.
- Apply mitigations according to vendor instructions, as CISA's required action states.
- Discontinue use of affected devices if mitigations are unavailable, following CISA's guidance.
- Review devices for signs of compromise, given known exploitation.
The CVE record names no fixed version, but that does not mean no fix exists. Consult the Google vendor advisory for the update that addresses this issue. Follow CISA's required action: apply mitigations per vendor instructions, and discontinue use of the product if mitigations are unavailable.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-693 Protection Mechanism Failure, CWE-285 Improper Authorization
Questions about CVE-2026-58704
- Is CVE-2026-58704 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-16, with a US federal due date of 2026-09-19. Whether it is used in ransomware campaigns is unknown.
- Does the attacker need user interaction or remote internet access?
- No user interaction is needed. The attack vector is adjacent network, so the attacker must be in proximal or adjacent range rather than anywhere on the internet.
- Which version fixes the issue?
- The CVE record names no fixed version. Refer to the Google vendor advisory to identify the Pixel security update that contains the fix.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.