dbcve.org
AndroidOperating system · Google

CVE-2026-0025

HIGH · 8.4 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 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 hasImage of Notification.java, there is a possible way to reveal information across users due to a permissions bypass. 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 an Android framework vulnerability in the hasImage method of Notification.java where a permissions bypass allows a local attacker to reveal information across different user profiles on the same device. The flaw enables local privilege escalation without requiring additional execution privileges or user interaction.

MitigationApply the Android security patch that addresses this Notification.java permissions bypass; users should install timely system updates from their device manufacturers.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/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
    Affected if The version listed is 14.0, 15.0, or 16.0 exactly
  2. Verify if multiple user profiles exist
    Go to Settings > System > Multiple users, or run 'pm list users' via ADB
    Affected if More than one user profile is configured on the device
  3. Confirm user profile switching is enabled
    Check Settings > System > Multiple users > Allow user switching, or inspect /data/system/users.xml for profile configurations
    Affected if Secondary user profiles are present and active on the device
  4. Check notification listener accessibility
    Inspect if apps can access notifications via NotificationListenerService; check Settings > Apps > Default apps > Messaging or run 'dumpsys notification' to view notification access grants
    Affected if Notification listeners are permitted and the device has multiple profiles configured

A device is affected if it runs Android 14.0, 15.0, or 16.0 AND has multiple user profiles enabled, as the vulnerability exploits the hasImage method in Notification.java to bypass profile isolation.

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 Android security patch that addresses this Notification.java permissions bypass; users should install timely system updates from their device manufacturers.

Recommended fix Moderate confidence

Android 14.0, 15.0, and 16.0 security patch levels as specified in the Android Security Bulletin (refer to source.android.com for the specific release date and patch level)

  1. Check the Android Security Bulletin for the month containing the fix for CVE-2026-0025 on source.android.com/security-bulletin
  2. Navigate to Settings > Security on the affected Android device
  3. Ensure the device has the latest Android system updates installed
  4. Check for and install any available security patch updates (look for the specific patch level that addresses this vulnerability)
  5. Verify the patch level after installation matches the fixed version released in the Android Security Bulletin
Caveat Security updates are generally backward-compatible and low-risk; however, ensure backup of important data before 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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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