CVE-2026-0061
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 · uneditedIn multiple functions of WindowState.java, 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 confidenceThis is an Android framework vulnerability in WindowState.java that allows tapjacking/overlay attacks to trick users into granting permissions. The vulnerability enables local privilege escalation without requiring additional execution privileges.
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= 14.0= 15.0= 16.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version is 14.0, 15.0, or 16.0 exactly, or falls within these major release lines without the CVE patch applied
-
Check security patch levelGo to Settings > About Phone > Security Patch Level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if The patch level predates the CVE-2026-0061 fix or shows as unknown/unavailable; a patched device will show a later date (the exact date varies by carrier/device)
-
Verify SYSTEM_ALERT_WINDOW permission statusGo to Settings > Apps > Special app access > Display over other apps, or run 'appops get SYSTEM_ALERT_WINDOW' via ADB shell to list apps with overlay permissionAffected if Any untrusted or unknown third-party application holds the SYSTEM_ALERT_WINDOW permission, which combined with the unpatched versions creates the exploit condition
-
Inspect WindowState.java patch status (if accessible)For ROM developers: review the framework/base/core/java/android/view/WindowState.java file in the device firmware, looking for validation logic added to prevent overlay on sensitive dialogsAffected if The code lacks proper validation checks in functions that handle window drawing over permission dialogs or system UI elements
A device is affected if it runs Android 14.0, 15.0, or 16.0 without the CVE-2026-0061 security patch applied and has apps with overlay permissions, allowing tapjacking attacks on sensitive UI elements.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Android framework security patches when available. Developers can use FLAG_SECURE on sensitive windows to prevent overlay capture. Users should apply system updates promptly.
- Consultation3.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0061 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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