CVE-2026-58704Google Pixel Improper Authorization Vulnerability
CVE-2026-58704 is a improper authorization in Google Pixel, rated high (8.8 on CVSS 3.1).
Why this priority: Exploited in the wild: listed in CISA's KEV catalog.
Published · Updated · NVD status: Analyzed
What it is
The software does not check, or checks wrongly, whether a caller may do something. A security control can be bypassed or does not work as intended.
How it is reached
An attacker can exploit it from the same local network segment, without an account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker reach data or actions their role should not allow.
Is it being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-16: it is being exploited in the wild. EPSS estimates a 0.62% chance of exploitation activity in the next 30 days, higher than 50% of scored CVEs.
What to do
- Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-09-19.
- No fixed version is listed yet. Find every place Google Pixel runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- Segment the networks that can reach it.
- Check exposed instances for signs of compromise, not only for the version.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
- Default settings, permissions and deployment configuration. The flaw sits between the shipped defaults and a hardened deployment.
Trust boundaries in play
- Local network segment. The attacker must share a network segment with the target.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
- Between the shipped defaults and a hardened deployment. An attacker who crosses it can use a weak default the deployment never changed.
Questions to answer about your own systems
- Where does Google Pixel run in your systems, and at which version?
- Which network segments can reach them?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.