dbcve.org
AndroidOperating system · Google

CVE-2026-0036

HIGH · 7.8 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In startAnimation of StageCoordinator.java, there is a possible tapjacking issue due to a tapjacking/overlay attack. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A tapjacking vulnerability in StageCoordinator.java's startAnimation method allows a malicious overlay to intercept touch events and perform unauthorized actions. An attacker with local access could draw malicious UI on top of legitimate application surfaces to trick users or intercept sensitive taps, achieving local privilege escalation without requiring additional execution privileges.

MitigationImplement FLAG_SECURE on sensitive windows and validate window tokens before processing touch events in StageCoordinator.java to prevent overlay attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 14.0= 15.0= 16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version
    Check Settings > About Phone > Android version. The affected versions are Android 14.0, 15.0, and 16.0.
    Affected if The device is running Android 14.0, 15.0, or 16.0
  2. Identify apps with overlay permission
    Check which apps hold the SYSTEM_ALERT_WINDOW permission. On Android 14+, go to Settings > Apps > Special app access > Display over other apps. On command line: adb shell dumpsys package <package_name> | grep SYSTEM_ALERT_WINDOW
    Affected if Any untrusted app has SYSTEM_ALERT_WINDOW permission granted, enabling it to draw overlays on top of the Stage Coordinator UI
  3. Confirm Stage Coordinator usage
    The vulnerability exists in StageCoordinator.java within the startAnimation method, which handles split-screen and multi-window transitions. Check if the device uses split-screen or multi-window features (recent Android devices support this by default).
    Affected if The device supports and uses Stage Coordinator functionality for window management, which is standard on Android 14+ devices
  4. Check for FLAG_SECURE implementation
    Examine the app or system UI components using StageCoordinator. Look for FLAG_SECURE window flag implementation: adb shell dumpsys window windows | grep -i secure. Also check source code for WindowManager.LayoutParams.FLAG_SECURE setting.
    Affected if FLAG_SECURE is NOT set on windows managed by StageCoordinator, meaning screenshot and overlay protection is not enabled

A user is affected if their device runs Android 14.0, 15.0, or 16.0 AND has apps with overlay permission AND the Stage Coordinator feature is active without FLAG_SECURE protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement FLAG_SECURE on sensitive windows and validate window tokens before processing touch events in StageCoordinator.java to prevent overlay attacks.

Recommended fix Moderate confidence

Android 17 or latest available release with corresponding security patch

  1. Upgrade the device to the latest Android version (Android 17 or later) that includes the security patch for this vulnerability
  2. Alternatively, ensure the device receives the latest Android Security Bulletin patch level that addresses this Stage Coordinator tapjacking vulnerability (CVE-2026-0036)
  3. Verify the patch level by checking Settings > About Phone > Security Patch Level
Caveat Upgrading to a major Android version may cause compatibility issues with existing apps or configurations; review app compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0036 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0036 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data