CVE-2025-21014VulnerabilityPublished 6 Aug 2025

CVE-2025-21014: Samsung Mobile Devices · : Improper Export of Android Application Components

Affects Samsung Mobile DevicesSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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:P/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 6 Aug 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-26.

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

To mitigate this vulnerability, European organizations should: 1) Ensure that all Samsung Mobile devices are updated promptly with the SMR August 2025 Release 1 or later, which addresses this vulnerability. 2) Implement strict physical security controls to prevent unauthorized local access to devices, including device lock policies, secure storage, and user awareness training to prevent social engineering that could trigger the vulnerability. 3) Restrict the installation of untrusted or unnecessary local applications that could exploit improperly exported components. 4) Monitor device logs and usage for unusual activity that may indicate attempts to access sensitive Emergency SoS components. 5) Employ Mobile Device Management (MDM) solutions to enforce security policies, control app permissions, and remotely wipe or lock devices if compromised or lost. 6) Educate users on the risks of interacting with unknown prompts or applications that could trigger this vulnerability. 7) Review and audit emergency-related data stored on devices to minimize sensitive information exposure where possible.

Description

Improper export of android application component in Emergency SoS prior to SMR Aug-2025 Release 1 allows local attackers to access sensitive information.

Impact

For European organizations, the impact of this vulnerability is primarily on the confidentiality of sensitive information stored or accessible via Samsung Mobile devices used within their environment. Since the vulnerability requires local access and user interaction, remote exploitation is not feasible, limiting large-scale attacks. However, in environments where devices are shared, lost, or physically accessed by unauthorized personnel, sensitive emergency-related data could be exposed. This could include personal emergency contacts, medical information, or location data, which may have privacy and regulatory implications under GDPR. Organizations relying on Samsung Mobile devices for critical communications or emergency response may face risks of data leakage or unauthorized data access. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely. However, the exposure of sensitive data could lead to reputational damage, compliance violations, and targeted social engineering attacks.

CWE-926Improper Export of Android Application Components (opens in a new tab)
Variant weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.
Build and Compilation · Attack Surface Reduction
If they do not need to be shared by other applications, explicitly mark components with android:exported="false" in the application manifest.
Build and Compilation · Attack Surface Reduction
If you only intend to use exported components between related apps under your control, use android:protectionLevel="signature" in the xml manifest to restrict access to applications signed by you.
Build and Compilation · Architecture and Design · Attack Surface Reduction
Limit Content Provider permissions (read/write) as appropriate.
OWASP Cheat Sheets
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.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=08 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Aug 2025, 05:04 UTC

WeaknessesCWE-926

Technical details

References

Community reviews

Related threats