Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Improper Input Validation in Android StrongBox importWrappedKey

IdentifiersCVE-2025-48651CWE-20· Improper Input Validation

CVE-2025-48651 is a high-severity vulnerability in the StrongBox component affecting Google and vendor implementations including NXP, STMicroelectronics, and Thales. According to the provided description, the flaw is in importWrappedKey of KMKeymasterApplet.java and results from improper input validation. A crafted wrapped-key import operation can cause access to cryptographic keys that should remain restricted. The issue impacts StrongBox, Android's hardware-backed key storage subsystem for protecting sensitive cryptographic material.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to local information disclosure by allowing access to restricted cryptographic keys or key material managed by StrongBox. Because StrongBox is intended to protect highly sensitive hardware-backed keys, disclosure may undermine confidentiality guarantees for protected secrets and any operations or data dependent on those keys. The provided content states exploitation requires no additional execution privileges and no user interaction.

Mitigation

If you can’t patch tonight, do this now.

Where patches cannot be applied immediately, reduce exposure by limiting local code execution on affected devices, restricting installation of untrusted applications, and enforcing strong application control and device management policies. Because the issue is local and affects access to protected keys, minimizing the ability of untrusted code to invoke StrongBox-backed key import paths is the primary interim mitigation. Information about any finer-grained vendor-specific workaround is not available in the provided content.

Remediation

Patch, then assume compromise.

Apply the April 2026 Android security updates. The provided content states that devices with security patch level 2026-04-05 or later address the issues covered in the bulletin, including CVE-2025-48651 where applicable. Vendors using affected StrongBox implementations from Google, NXP, STMicroelectronics, or Thales should integrate the corresponding fixes for their platform.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.