In navigateUpTo of ActivityClientController.java, there is a possible permission bypass due to a logic error in the code.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 16, 16-qpr2, 17
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 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? →
- 14/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? →
- Specific setups only
- Fix
- Fixed in 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
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
Read the original 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
Upgrade to a fixed version: 16, 16-qpr2, 17.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Google Android
17, 16-qpr2, 16
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58946
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: source.android.com
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: source.android.com
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: 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