CVE-2026-58704
CVE-2026-58704 is a security flaw in Google Pixel, the software on Google’s Pixel phones. Someone who already has a foothold can use Google Pixel to take full control of the machine. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 16 Sep 2026.[1]
Google Pixel is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Google has published a fix or advice.
Description
CISA calls it an improper authorization in Google Pixel. In its words: “Google Pixel devices contain an improper authorization vulnerability in the cellular modem. A logic error may allow an attacker to bypass permission checks and escalate privileges.”[1]
The CVE record adds: “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.”[2]
The underlying weakness is protection mechanism failure (CWE-693), in MITRE’s list of common software weaknesses.
It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record doesn’t list version ranges for it; Google’s advisory has them[3]. CISA names the product as Google Pixel.
Every device with Google Pixel needs the update.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 16 Sep 2026, within a day of it being made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 19 Sep 2026 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at under 1%. That’s in the top 51% of the flaws it scores.[4]
CISA assesses it as not automatable: each attack takes some work.
CISA doesn’t say who was attacked, or how.
Fix
Google has published a fix or advice.[3] CISA’s required action: “Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes).”[1]
- Update Google Pixel now.On Android: Settings, then System or Software update. Phones only get these fixes while their maker still supports them. Then turn on automatic updates, so the next fix arrives on its own.
- If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at under 1%.[4] |
See also
Other Google Pixel flaws
- CVE-2021-39793: out-of-bounds write ·
Other Google flaws
- CVE-2026-111497, Google Brotli: unchecked return value ·
- CVE-2026-87491, Chrome and other Chromium browsers: out of bounds write ·
- CVE-2026-85046, Chrome and other Chromium browsers: type confusion ·
- CVE-2026-11645, Chrome and other Chromium browsers: out-of-bounds read and write ·
- CVE-2026-5281, Google Dawn: use-after-free ·
Other protection mechanism failure flaws
- CVE-2026-32202, Microsoft Windows: protection mechanism failure ·
- CVE-2025-40536, SolarWinds Web Help Desk: security control bypass ·
- CVE-2026-21513, Microsoft Windows: MSHTML framework protection mechanism failure ·
- CVE-2026-21510, Microsoft Windows: shell protection mechanism failure ·
- CVE-2025-0411, 7-Zip: mark of the web bypass ·
Added the same day
- CVE-2026-87886, Acronis Backup: incorrect default permissions ·
- CVE-2026-76460, Cisco Identity Services Engine: incorrect use of privileged APIs ·
Every Google flaw on CISA’s list · Everything added in September 2026
References
- ^ Cybersecurity and Infrastructure Security Agency. “Google Pixel Improper Authorization Vulnerability”. Known Exploited Vulnerabilities Catalog, added 16 Sep 2026.
- ^ National Institute of Standards and Technology. “CVE-2026-58704 Detail”. National Vulnerability Database, published 15 Sep 2026.
- ^ Google. Advisories and fixes: source.android.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.006, percentile 50.0, 31 Oct 2026.
- CVE Program. “CVE-2026-58704”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.