Skip to main content
← Vulnerabilities

In handlePackagePostInstall of InstallPackageHelper.java, there is a possible Enhanced Confirmation Mode (ECM) bypass vulnerability that…

7.8HighCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 16, 16-qpr2, 17
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affects Android versions 16, 16-qpr2 and 17 (per the advisory's updated AOSP versions column).

Published
Last modified
Published
Not listed in CISA KEV
14/100 · provisional
Specific setups only
Fix
Fixed in 16, 16-qpr2, 17
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

In handlePackagePostInstall of InstallPackageHelper.java, there is a possible Enhanced Confirmation Mode (ECM) bypass vulnerability that allows a sideloaded application to modify the package source during a self-update due to a logic error in the code. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.

What to do

  • Check whether your setup matches what the bug needs.

    Affects Android versions 16, 16-qpr2 and 17 (per the advisory's updated AOSP versions column).
  • Upgrade to a fixed version: 16, 16-qpr2, 17.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • Google Android

    17, 16-qpr2, 16

Evidence 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-58836

What does this mean?

The bug is an Enhanced Confirmation Mode (ECM) bypass in the handlePackagePostInstall function of InstallPackageHelper.java, which lets the protection that ECM provides be circumvented. The advisory's impact statement is not available in the checked facts.Source: source.android.com

Am I affected, and how do I check?

The advisory lists Android versions 16, 16-qpr2 and 17. To check, look up the Android version shown in the device's system settings and compare it with those three versions.Source: source.android.com

What should I do about it?

Install the Android security update for the 16, 16-qpr2 or 17 line that includes the fix. The advisory lists these versions as fixed.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