CVE-2026-28656 Google CVE debrief

Who should care

Defenders responsible for managing and securing Google Android devices, particularly those running Android 14.0, 15.0, and 16.0, should assess exposure and prioritize patching. Vulnerability management teams, security operations teams, and IT administrators should review and apply patches for affected versions to prevent potential escalation of privilege. Additionally, defenders should conduct thorough vulnerability assessments to identify exposed devices,

Why it matters

CVE-2026-28656 is a high-severity vulnerability in Google Android that allows for local escalation of privilege through a tapjacking/overlay attack, requiring user interaction for exploitation. Defenders should prioritize verifying and applying patches for affected versions.

• Verify and apply patches for affected Google Android versions to prevent potential escalation of privilege
• Conduct thorough vulnerability assessments to identify exposed devices and prioritize remediation
• Implement compensating controls to mitigate potential impacts of successful exploitation

Technical summary

The vulnerability exists in multiple functions of DeviceAdminAdd.java, allowing for a tapjacking/overlay attack that could lead to local escalation of privilege with no additional execution privileges needed. User interaction is required for exploitation. The vulnerability is rated with a CVSS score of 7.3 and affects Google Android versions 14.0, 15.0, and 16.0. Defenders should prioritize verifying and applying patches for these versions to prevent potential escalation of privilege. The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and affected versions.

Defensive priority

Defenders should prioritize verifying and applying patches for affected Google Android versions, particularly for devices running Android 14.0, 15.0, and 16.0.

Recommended defensive actions

• Verify and apply patches for affected Google Android versions
• Conduct thorough vulnerability assessments to identify exposed devices
• Implement compensating controls to mitigate potential impacts
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and affected versions. However, specific details on exploitation or victim impact are limited. The vulnerability is confirmed to exist in multiple functions of DeviceAdminAdd.java, and defenders should verify and apply patches for affected Google Android versions. The CVE record was published on 2026-09-08T19:17:56.100Z and has not been modified since then. Limited information is available on potential victim impact or exploitation attempts.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.