dbcve.org
AndroidOperating system · Google

CVE-2026-0007

HIGH · 8.6 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges

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 writeToParcel of WindowInfo.cpp, there is a possible way to trick a user into accepting a permission 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/overlay vulnerability in Android's WindowInfo.cpp writeToParcel method allows a malicious app to potentially intercept or manipulate permission dialogs by overlaying deceptive UI elements, leading to local privilege escalation without requiring user interaction.

MitigationApply the vendor-provided security patch to Android Framework; ensure overlay permission restrictions are properly enforced and verify that WindowInfo serialization includes anti-tapjacking protections.

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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The device runs Android 14.0, 15.0, or 16.0 exactly (the affected versions listed)
  2. Check SYSTEM_ALERT_WINDOW permission status
    Navigate to Settings > Apps > Special app access > Display over other apps, or inspect with 'dumpsys package com.android.systemui' and look for SYSTEM_ALERT_WINDOW in granted permissions
    Affected if Any app has been granted SYSTEM_ALERT_WINDOW permission, which enables overlay capabilities required for tapjacking exploitation
  3. Review overlay permission settings
    Check Settings > Apps > Special app access > Display over other apps to see which apps can draw over other apps
    Affected if Apps unknown to the user or untrusted applications have overlay permissions enabled
  4. Inspect app overlay permissions programmatically
    Use ADB command 'appops get <package_name> SYSTEM_ALERT_WINDOW' to check specific app overlay permissions
    Affected if Any non-system application has SYSTEM_ALERT_WINDOW allowed or ignored (not denied)

A device is affected if it runs Android 14.0, 15.0, or 16.0 AND has applications with overlay (SYSTEM_ALERT_WINDOW) permissions granted, as the vulnerability enables tapjacking attacks through WindowInfo serialization.

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

Apply the vendor-provided security patch to Android Framework; ensure overlay permission restrictions are properly enforced and verify that WindowInfo serialization includes anti-tapjacking protections.

Recommended fix Moderate confidence

Latest Android security patch level (monthly security update containing the fix for CVE-2026-0007)

  1. 1. Check your Android device's current security patch level by going to Settings > About Phone > Android version or Settings > Security > Security update
  2. 2. Apply the latest Android security update for your device. For Pixel devices, go to Settings > System > Software update
  3. 3. If your device manufacturer has released a specific patch for CVE-2026-0007, install that update
  4. 4. Verify the security patch level has been updated after installation
Caveat Security updates typically have minimal breaking changes; some older apps may need updates for compatibility with UI layer restrictions

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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