CVE-2026-28607

Google · Android

A confused deputy vulnerability in Android allows for background activity launch bypass, enabling local escalation of privilege without user interaction.

Executive summary

A high-severity local escalation of privilege vulnerability in Google Android allows attackers to bypass background activity restrictions, potentially granting unauthorized system access.

Vulnerability

The flaw arises from a confused deputy mechanism within multiple system functions, which permits a local attacker with low privileges to bypass background activity launch restrictions. This vulnerability does not require user interaction to trigger, facilitating an escalation of privilege.

Business impact

Successful exploitation of this vulnerability allows a local actor to gain elevated privileges on affected Android devices, which could lead to unauthorized access to sensitive user data, application bypasses, or complete system compromise. Given the CVSS score of 7.8, this vulnerability poses a significant risk to the integrity and confidentiality of the mobile environment, particularly in enterprise deployments where device security is paramount.

Remediation

Immediate Action: Administrators should monitor for the release of official security patches from Google or original equipment manufacturers and apply them to all managed Android devices as soon as they become available.

Proactive Monitoring: Security teams should review device logs for unusual activity or unexpected background process execution that may indicate an attempt to exploit system-level functions.

Compensating Controls: Ensure that enterprise mobility management (EMM) policies are strictly enforced to limit the installation of untrusted applications, which serves as a primary vector for local exploitation attempts.

Exploitation status

Public Exploit Available: No

Analyst recommendation

This vulnerability represents a significant risk to Android device security due to the potential for privilege escalation without user awareness. Organizations should prioritize updating their device fleets to the latest security patch levels provided by Google to neutralize this threat and prevent unauthorized system modification.

More Google CVEs all →

History

CVE Brief tracked this CVE 2 days before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 7.8 (3.1)
  4. Analyst report written

Sources