In multiple locations, there is a possible permission bypass due to an uncaught exception.
- Exploited
- No known exploitation
- Fix
- Fixed in 14, 15, 16, 16-qpr2, 17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 14, 15, 16, 16-qpr2, 17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In multiple locations, there is a possible permission bypass due to an uncaught exception. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
What to do
Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17, 16-qpr2, 16, 15, 14
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-59004
What does this mean?
The bug is a permission bypass caused by an uncaught exception in several places in Android. The advisory classifies it as escalation of privilege (EoP) and rates it High.Source: source.android.com
Am I affected, and how do I check?
The advisory table lists Android 14, 15, 16, 16-qpr2 and 17 for this CVE. To check a device, a reader can look under Settings, About phone, for the Android version and security patch level.Source: source.android.com
What should I do about it?
Install the latest Android security update for the version in use, since the advisory table lists these versions as covered by the fix. The source gives no specific patched build number, so the update should be confirmed against Google's security bulletin.Source: source.android.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data