CVE-2025-20991VulnerabilityPublished 4 Jun 2025

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

Affects Samsung Mobile DevicesSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 08:30 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:N/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 4 Jun 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 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-20991, European organizations should: 1) Prioritize the deployment of the Samsung Mobile June 2025 Security Maintenance Release (SMR) Release 1 or later updates as soon as they become available to ensure the vulnerability is patched. 2) Implement strict Bluetooth usage policies, including disabling Bluetooth discoverability when not in use, especially in sensitive or high-risk environments. 3) Enforce device configuration management to restrict Bluetooth settings and prevent unauthorized changes by users. 4) Educate employees on the risks of leaving Bluetooth enabled and discoverable in public or unsecured locations. 5) Utilize Mobile Device Management (MDM) solutions to monitor and control Bluetooth settings remotely, allowing centralized enforcement of security policies. 6) Conduct regular security audits and vulnerability assessments on mobile devices to detect misconfigurations or signs of exploitation. 7) Consider physical security controls to limit unauthorized local access to devices, such as secure storage or access controls in workplaces. These measures go beyond generic advice by focusing on operational controls, user behavior, and proactive patch management tailored to the specific nature of this Bluetooth-related vulnerability.

Description

Improper export of Android application components in Bluetooth prior to SMR Jun-2025 Release 1 allows local attackers to make devices discoverable.

Impact

For European organizations, the impact of CVE-2025-20991 is primarily related to the potential for unauthorized Bluetooth discovery and pairing attempts on Samsung Mobile devices used within corporate environments. This could lead to unauthorized access to device features or data leakage through Bluetooth channels if paired devices are exploited. While the vulnerability does not directly compromise confidentiality or availability, it could serve as an initial vector for further attacks, especially in environments where sensitive data is accessed via mobile devices. Organizations with Bring Your Own Device (BYOD) policies or those that rely heavily on Samsung smartphones for field operations, secure communications, or mobile workforce management may face increased risk. The local attack requirement limits the threat to scenarios where an attacker has physical proximity or access, such as in public spaces, offices, or transit hubs. This vulnerability could also undermine trust in device security, potentially affecting compliance with data protection regulations like GDPR if unauthorized data access occurs. Additionally, the improper export of components could be leveraged in combination with other vulnerabilities to escalate attacks, making it a concern for layered security strategies.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Jul 2025, 00:09 UTC

WeaknessesCWE-926

Technical details

References

Community reviews

Related threats