Security readout for executives and security teams
Plain-English summary
CVE-2025-48651 is an Android SoC issue in Keymaster key import handling. A local attacker may be able to access keys that should remain restricted. The known impact is limited information disclosure, not device takeover or service disruption.
Executive priority
Treat this as a patch-management priority for Android fleets, especially devices handling sensitive credentials. It is moderate severity because impact is limited to confidentiality and requires local access, but key exposure can still create business risk.
Technical view
The flaw is improper input validation in importWrappedKey within KMKeymasterApplet.java. The CVSS vector is local, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality impact only. Integrity and availability impacts are not reported.
Likely exposure
Exposure is most relevant to Android devices using affected SoC Keymaster implementations covered by the April 2026 Android security bulletin. The provided data does not identify specific device models, OEMs, or chipsets.
Exploitation context
The record describes local exploitation with no privileges or user interaction required. It is not listed in KEV, and the provided sources do not state active exploitation or public exploit availability.
Researcher notes
Evidence is limited to the CVE record and Android bulletin reference. Do not assume affected models, exploitability beyond local disclosure, or available mitigations not named by Google or OEMs.
Mitigation direction
- Check Google and OEM guidance for CVE-2025-48651.
- Apply the relevant Android security update when available for each device.
- Prioritize managed Android devices that store sensitive keys or business credentials.
- Track OEM patch release status for affected device fleets.
Validation and detection
- Inventory Android devices and current security patch levels.
- Compare device patch status with the April 2026 Android security bulletin.
- Confirm OEM advisories for device-specific SoC exposure.
- Review MDM compliance reports for unpatched or unsupported devices.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-48651 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N2.51.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
4MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/docs/security/bulletin/2026/2026-04-01CVE reference, google_android · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.