VulnerabilityPublished 8 Jul 2025

CVE-2025-21003: 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 26 Oct 2026, 12:55 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 3% 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 8 Jul 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

To mitigate CVE-2025-21003, European organizations should: 1) Ensure all Samsung Mobile devices are updated promptly to the SMR July 2025 Release 1 or later, which addresses this vulnerability. 2) Enforce strict physical security controls to prevent unauthorized local access to devices, including device lock policies, secure storage, and employee training on device handling. 3) Implement mobile device management (MDM) solutions that can enforce encryption and restrict access to sensitive features like Emergency SOS data. 4) Regularly audit devices for compliance with security policies and verify that sensitive data is not stored insecurely. 5) Educate users about the risks of local data exposure and encourage immediate reporting of lost or stolen devices. 6) Consider disabling or limiting Emergency SOS features if they are not critical to business operations until devices are patched. 7) Monitor for any future advisories or exploit reports related to this vulnerability to respond swiftly. These steps go beyond generic advice by focusing on the specific vector of local access and the nature of the Emergency SOS feature.

Description

Insecure storage of sensitive information in Emergency SOS prior to SMR Jul-2025 Release 1 allows local attackers to access sensitive information.

Impact

For European organizations, the impact of CVE-2025-21003 depends largely on the use of Samsung Mobile devices within their workforce and the sensitivity of data stored or accessible via the Emergency SOS feature. Organizations with employees who carry Samsung devices for business purposes may face risks of sensitive personal or emergency-related information leakage if devices are lost, stolen, or accessed by unauthorized personnel locally. While the vulnerability does not allow remote exploitation, the risk of data exposure in scenarios involving physical device compromise is significant. This could lead to privacy violations under GDPR if personal data is exposed, resulting in regulatory penalties and reputational damage. Additionally, emergency-related data leakage could undermine employee safety protocols or expose medical information. The vulnerability does not directly threaten system integrity or availability, so operational disruption is unlikely. However, organizations in sectors with high privacy requirements—such as healthcare, finance, or government—should be particularly cautious. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed proactively to prevent future exploitation.

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=07 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 10:59 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats