dbcve.org
AndroidOperating system · Google

CVE-2025-48651

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 importWrappedKey of KMKeymasterApplet.java, there is a possible way access keys that should be restricted due to improper input validation. This could lead to local information disclosure 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 vulnerability exists in the importWrappedKey function of KMKeymasterApplet.java, which handles importing encrypted (wrapped) keys into Android's Keymaster hardware abstraction layer. Due to improper input validation, an attacker could potentially access keys that should have been restricted, leading to local information disclosure without requiring user interaction or elevated privileges.

MitigationApply the security patch from the Android monthly security bulletin for the affected version. Since this is in the Keymaster applet (hardware-backed key storage), device manufacturers must integrate the vendor-specific patch into their system images.

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:all versions

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 Keymaster TA presence
    Check if the device has a TEE (Trusted Execution Environment) running Keymaster. On rooted devices, examine /vendor/etc/teeos/ or /system/etc/teegris/ directories for Keymaster trusted application binaries, or check /sys/class/misc/tee* for TEE device nodes.
    Affected if Device has a TEE with Keymaster TA implemented and the importWrappedKey function is exposed through Keymaster HAL interface.
  2. Confirm importWrappedKey operation availability
    Use keymaster_cmdline tool or check Keymaster HAL service status. Run 'keymaster_hal --list' or examine /vendor/lib/hw/keymaster*.so to identify if the importWrappedKey keymint operation is exposed.
    Affected if The importWrappedKey/keymint operation is exposed and accessible to local applications without additional privilege checks.
  3. Check Android security patch level
    Run 'getprop ro.build.version.security_patch' or check Settings > About Phone > Android security patch level to determine the installed patch version.
    Affected if Security patch level is earlier than the vendor-specific patch addressing this vulnerability (noting that 'all versions' are listed as affected, so most unpatched systems are vulnerable).
  4. Identify applications with key import permissions
    Review app permissions via 'dumpsys package' for apps holding IMPORT_KEY or similar key management permissions, and check if any app can invoke Keymaster via KeyChain API or KeyMint HAL.
    Affected if Any local application without elevated privileges can access the importWrappedKey function due to missing input validation on key restriction attributes.

The environment is affected if the device runs any Android version with Keymaster TA present and has not received a vendor-specific security patch addressing the improper input validation in the importWrappedKey function.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the security patch from the Android monthly security bulletin for the affected version. Since this is in the Keymaster applet (hardware-backed key storage), device manufacturers must integrate the vendor-specific patch into their system images.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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