CVE-2025-21045VulnerabilityPublished 10 Oct 2025

CVE-2025-21045: Samsung Mobile Devices · Insecure Storage of Sensitive Information

Affects Samsung Mobile DevicesSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.0Medium

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.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Ensure all Samsung Galaxy Watch devices are updated promptly to the SMR Oct-2025 Release 1 or later firmware once available, as this update is expected to address the insecure storage issue. 2. Implement strict physical security controls to prevent unauthorized local access to wearable devices, including secure storage when not in use and policies restricting device sharing. 3. Enforce device encryption and strong authentication mechanisms on paired smartphones and watches to limit data exposure if devices are lost or stolen. 4. Educate employees about the risks of leaving wearable devices unattended and the importance of reporting lost or stolen devices immediately. 5. Consider disabling or limiting sensitive data storage on wearable devices in high-security environments until patches are applied. 6. Monitor for unusual access patterns or attempts to access device data locally, integrating wearable device security into broader endpoint protection strategies. 7. Collaborate with Samsung support channels to obtain timely updates and security advisories related to this vulnerability.

Description

Insecure storage of sensitive information in Galaxy Watch prior to SMR Oct-2025 Release 1 allows local attackers to access sensitive information.

Impact

For European organizations, the primary impact of CVE-2025-21045 lies in the potential exposure of sensitive information stored on Samsung Galaxy Watch devices. This could include personal health data, corporate credentials, or other confidential information that, if accessed by unauthorized local actors, may lead to privacy violations or facilitate further attacks. The vulnerability does not affect device integrity or availability, so operational disruption is unlikely. However, in sectors such as healthcare, finance, or government where data confidentiality is paramount, the risk of data leakage could have regulatory and reputational consequences under GDPR and other privacy laws. The requirement for local access limits remote exploitation but raises concerns in scenarios where devices are lost, stolen, or accessed by insiders. Organizations with policies allowing wearable device use in sensitive environments should consider this vulnerability a moderate risk. The lack of known exploits reduces immediate threat levels but does not eliminate the need for proactive mitigation, especially as the vulnerability could be leveraged in targeted attacks or physical compromise scenarios.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.samsungmobile.com/securityUpdate.smsb?year=2025&month=10 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 10 Oct 2025, 06:45 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats