dbcve.org
AndroidOperating system · Google

CVE-2026-0093

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 multiple locations, there is a possible misleading UI due to obfuscation. 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 UI obfuscation vulnerability exists in multiple locations that allows a local attacker to escalate privileges by misleading the system through deceptive user interface elements. The flaw requires no user interaction and no additional execution privileges, making it a straightforward local privilege escalation vector.

MitigationConduct a comprehensive code audit across all identified locations to identify and remove UI obfuscation, ensuring all interface elements are properly rendered with clear, unambiguous labels and visual indicators.

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. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The installed version equals 14.0, 15.0, or 16.0 exactly
  2. Check for UI overlay permissions granted
    Go to Settings > Apps > Special app access > Display over other apps, or run 'adb shell dumpsys package <package_name> | grep SYSTEM_ALERT_WINDOW' for specific apps
    Affected if Apps have SYSTEM_ALERT_WINDOW or android.permission.SYSTEM_ALERT_WINDOW permission granted, especially untrusted apps
  3. Check accessibility services configuration
    Go to Settings > Accessibility > Installed services, or run 'adb shell dumpsys accessibility' to list active services
    Affected if Any accessibility service is enabled that could intercept or manipulate UI elements for privilege escalation
  4. Review apps with window token permissions
    Run 'adb shell dumpsys package' and search for packages with android.permission.INTERNAL_SYSTEM_WINDOW or similar window-related permissions
    Affected if Any app holds permissions allowing creation of windows that could overlay system UI elements
  5. Audit UI-related app permissions
    Run 'adb shell pm list permissions -g' and inspect permissions in the 'UI' or 'Display' groups
    Affected if Apps hold permissions that allow manipulation of system UI surfaces without explicit user validation

A user is affected if their Android device runs version 14.0, 15.0, or 16.0 and has any third-party apps with overlay, accessibility, or window management permissions that could be exploited through UI obfuscation techniques.

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

Conduct a comprehensive code audit across all identified locations to identify and remove UI obfuscation, ensuring all interface elements are properly rendered with clear, unambiguous labels and visual indicators.

Recommended fix Moderate confidence

Latest Android security update (security patch level containing fix for CVE-2026-0093)

  1. 1. Check the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  2. 2. Ensure the device receives and installs the latest Android security update
  3. 3. For Android 14.0 devices: Update to the latest available security patch level (typically addressing vulnerabilities in the framework)
  4. 4. For Android 15.0 devices: Update to the latest available security patch level
  5. 5. For Android 16.0 devices: Update to the latest available security patch level
  6. 6. If OTA updates are unavailable, check with device OEM for available firmware updates containing the fix
Caveat Security updates typically have minimal breaking changes; however, verify app compatibility after applying system updates

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0093 — 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-0093 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