Skip to main content
CVE-2025-21020VulnerabilityPublished Updated

CVE-2025-21020: Samsung Mobile Blockchain Keystore · Out-of-bounds Write

Affects Samsung Mobile Blockchain KeystoreSource CVE Database V5

0

Not known to be exploited · CVSS 5.7 Medium : upgrade to 1.3.17.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.17.2
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Samsung Mobile Blockchain Keystore to 1.3.17.2.

Affected software

ProductAffectedFixed in
Samsung Mobile Blockchain KeystoreAffected
  • <1.3.17.2
Fixed in
  • 1.3.17.2

AI-suggested

To mitigate CVE-2025-21020, organizations and users should: 1) Monitor Samsung's official channels for the release of a security patch or updated Blockchain Keystore version (1.3.17.2 or later) and apply it promptly once available. 2) Restrict local privileged access on Samsung mobile devices to trusted personnel only, minimizing the risk of local exploitation. 3) Implement strong endpoint security controls to prevent privilege escalation by malware or unauthorized users. 4) Employ device management policies that enforce application whitelisting and limit installation of untrusted software. 5) Regularly audit device logs and keystore access patterns to detect suspicious activity indicative of exploitation attempts. 6) Educate users about the risks of granting elevated privileges to applications or users. 7) Consider isolating blockchain-related operations on dedicated devices or environments to reduce exposure. These steps go beyond generic advice by focusing on controlling local privilege and monitoring keystore integrity.

Description

Out-of-bounds write in creating bitmap images in Blockchain Keystore prior to version 1.3.17.2 allows local privileged attackers to write out-of-bounds memory.

References

Community reviews

Loading reviews…