VYPR
Unrated severityNVD Advisory· Published Jun 1, 2026

CVE-2026-0036

CVE-2026-0036

Description

A tapjacking vulnerability in Android's StageCoordinator allows local privilege escalation without user interaction or additional execution privileges.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A tapjacking vulnerability in Android's StageCoordinator allows local privilege escalation without user interaction or additional execution privileges.

Vulnerability

A tapjacking issue exists in startAnimation of StageCoordinator.java within Android. This vulnerability is due to a tapjacking or overlay attack, potentially allowing for local privilege escalation. The vulnerability affects Android versions covered by the June 2026 security bulletin [1].

Exploitation

Exploitation of this vulnerability does not require user interaction. An attacker could leverage a tapjacking or overlay attack to trick the user into interacting with a malicious UI element that is overlaid on top of a legitimate application's interface. This could lead to the execution of unintended actions or the escalation of privileges.

Impact

Successful exploitation of this vulnerability could lead to a local escalation of privilege. The attacker gains elevated privileges on the device without needing any additional execution privileges beyond what is required to initiate the tapjacking attack. This means an attacker could potentially gain access to sensitive system functions or data.

Mitigation

This vulnerability is addressed in the June 2026 Android Security Bulletin [1]. Users should ensure their devices are updated to the patched versions. Specific patch release dates and workarounds are detailed in the official Android security bulletin.

AI Insight generated on Jun 1, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.