dbcve.org
AndroidOperating system · Google

CVE-2025-0080

HIGH · 7.8 CVSS v3.1 Published 2025-08-26
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 way to overlay the installation confirmation dialog 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

This is a tapjacking/overlay vulnerability affecting Android's installation confirmation dialog in multiple locations. A malicious app can overlay the installation dialog without requiring user interaction, potentially leading to unauthorized app installations or privilege escalation by tricking the system into confirming malicious actions.

MitigationImplement overlay detection and prevention by using FLAG_SECURE window flags on sensitive dialogs, validating touch events for potential overlay interference, and ensuring proper handling of SYSTEM_ALERT_WINDOW permissions to block malicious overlays on installation prompts.

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:= 15.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
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' in ADB shell
    Affected if The device is running Android 15.0 exactly (version = 15.0)
  2. Check installed apps with overlay permission
    Go to Settings > Apps > Special access > Display over other apps. Alternatively, run 'adb shell appops list' to enumerate apps with SYSTEM_ALERT_WINDOW permission
    Affected if Any untrusted or third-party app is granted the 'Display over other apps' (SYSTEM_ALERT_WINDOW) permission
  3. Review apps with installation interaction access
    Check Settings > Apps > Special access > Install unknown apps. Identify which apps have permission to install packages
    Affected if Apps with install permissions also have overlay permissions, creating a path for exploitation
  4. Check security patch level
    Go to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch'
    Affected if The security patch level is earlier than the patch that addresses this CVE in Android 15.0 (if available)

The environment is affected if the device runs Android 15.0 AND has apps with SYSTEM_ALERT_WINDOW or 'Display over other apps' permissions that could overlay installation dialogs.

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 overlay detection and prevention by using FLAG_SECURE window flags on sensitive dialogs, validating touch events for potential overlay interference, and ensuring proper handling of SYSTEM_ALERT_WINDOW permissions to block malicious overlays on installation prompts.

Recommended fix Moderate confidence

Any subsequent Android 15.x security update or Android 16.0 and later

  1. 1. Go to Settings on the Android device
  2. 2. Navigate to System > Software Update (or Settings > About Phone > Software Update)
  3. 3. Check for updates and download any available security updates
  4. 4. Install the latest Android security patch level available for your device
  5. 5. After updating, verify the device is running a version newer than Android 15.0 by checking Settings > About Phone > Android version
Caveat Security updates typically have minimal breaking changes; however, some app compatibility issues may arise with newer Android versions

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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