CVE-2026-0091: High severity Google Android vulnerability

Published Jun 1, 2026
·
Updated

In multiple locations, there is a possible way to execute code in the launcher process due to an over-privileged shell user. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Affected Software

6 affected components
Google Android=14.0
Google Android=15.0
Google Android=16.0
Google Android=16.0-qpr2_beta_1
Google Android=16.0-qpr2_beta_2
Google Android=16.0-qpr2_beta_3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove over-privileged shell user from your environment.

    If the shell user is not required, remove the account and any associated credentials from systems to eliminate the privilege source.

  2. Configuration

    Remove unnecessary privileges from the over-privileged shell user: remove it from privileged groups, eliminate unnecessary sudoers entries, and remove setuid bits or elevated capabilities so the account cannot be used to execute code in privileged processes.

    shell user privileges = least-privilege (remove unnecessary elevated privileges)
  3. Configuration

    Ensure the launcher process does not run with the shell user's elevated privileges. Run the launcher as a dedicated unprivileged account or drop privileges early during startup to prevent code execution via an over-privileged shell user.

    launcher process run_as_user = unprivileged user / drop privileges at startup
  4. Compensating control

    Restrict access to local accounts and interactive shell access via host-based controls (SSH allowlists, PAM restrictions, limiting which accounts can log in, firewall/ACLs) and require strong authentication to reduce the risk of local exploitation.

  5. Operational

    Audit system logs and account activity for signs of local code execution or privilege escalation; if compromise is suspected, isolate affected hosts, remediate, and rotate impacted credentials.

Event History

Jun 1, 2026
CVE Published
via MITRE·09:14 PM
Data Sourced
via MITRE·09:14 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-0091?

CVE-2026-0091 has a high severity rating of 7.8 according to the CVSS 3.1 scoring system.

2

How do I fix CVE-2026-0091?

To mitigate CVE-2026-0091, ensure your Google Android device is updated to the latest security patch that addresses this vulnerability.

3

What impact does CVE-2026-0091 have?

CVE-2026-0091 can lead to local escalation of privileges, allowing an attacker to execute code in the launcher process.

4

Is user interaction required to exploit CVE-2026-0091?

No, user interaction is not required to exploit CVE-2026-0091.

5

What is the primary cause of CVE-2026-0091?

CVE-2026-0091 is caused by an over-privileged shell user in multiple locations within the Google Android system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203