dbcve.org
AndroidOperating system · Google

CVE-2025-22422

HIGH · 7.8 CVSS v3.1 Published 2025-09-02
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 mislead a user into approving an authentication prompt for one app when its result will be used in another due to a logic error in the code. 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 logic error in authentication prompt handling allows an attacker to trick the system into using authentication results intended for one application in another context, leading to local privilege escalation. This occurs across multiple code locations where the association between authentication prompts and their target applications is not properly validated.

MitigationFix the authentication flow logic to ensure prompts are correctly bound to their intended target application and verify the authentication context before accepting results. Review all locations where authentication results are consumed.

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:= 13.0= 14.0= 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' via ADB shell
    Affected if The version is exactly 13.0, 14.0, or 15.0 (not a later security patch release that may contain the fix)
  2. Confirm biometric or credential authentication is in use
    Check Settings > Security > biometrics or any app that uses fingerprint/face/password authentication
    Affected if Any biometric or credential-based authentication is enrolled and active on the device
  3. Identify applications using authentication prompts
    Review installed apps for any that request biometric, PIN, password, or other credential-based authentication
    Affected if Multiple applications that trigger authentication prompts are installed on the device
  4. Check for third-party authentication libraries
    Inspect installed apps for use of biometric APIs (android.hardware.biometrics) or Keystore authentication, which could be affected by improper prompt binding
    Affected if Applications using Android's built-in authentication frameworks are present

A user is affected if their device runs Android 13.0, 14.0, or 15.0 and uses any authentication-protected features, as the logic flaw allows authentication results to be improperly redirected between applications.

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

Fix the authentication flow logic to ensure prompts are correctly bound to their intended target application and verify the authentication context before accepting results. Review all locations where authentication results are consumed.

Recommended fix Moderate confidence

Latest available Android security update for Android 13.0/14.0/15.0 (typically the February 2025 Android Security Bulletin or later)

  1. 1. Check your current Android version by going to Settings > About Phone > Android version
  2. 2. Check your current security patch level by going to Settings > About Phone > Security patch level
  3. 3. Update your device to the latest available Android security update for your version (13.0, 14.0, or 15.0)
  4. 4. On Pixel devices, go to Settings > System > Software update to check for updates
  5. 5. On other Android devices, check with your device manufacturer's update channels
  6. 6. Verify the security patch level has been updated to include the fix for CVE-2025-22422
Caveat Standard Android update risks - ensure backup of data before applying, some custom ROMs may not receive official patches

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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