VulnerabilityPublished 5 Nov 2025Updated 7 Nov 2025

CVE-2025-21076: Samsung Account · Improper Handling of Insufficient Permissions or Privileges

Affects Samsung AccountSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 15.5.00.18 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.5Medium

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 15.5.00.18

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

Attack Vector: Local
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: 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: 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 5 Nov 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

Upgrade Samsung Account to 15.5.00.18.

Affected software

Product	Affected	Fixed in
Samsung Mobile Samsung Account	Affected <15.5.00.18	Fixed in 15.5.00.18

AI-suggested

European organizations should prioritize updating Samsung Account to version 15.5.00.18 or later as soon as the patch is available to address this vulnerability. Until patches are deployed, organizations should enforce strict physical security controls to prevent unauthorized local access to mobile devices, including device lock policies, biometric authentication, and secure storage. User awareness training should emphasize the risks of social engineering or inadvertent user actions that could trigger the vulnerability. Mobile device management (MDM) solutions can be used to monitor and restrict installation of untrusted applications and enforce security policies. Additionally, organizations should audit and limit the use of Samsung Account features on corporate devices where feasible, or consider alternative secure authentication and synchronization methods. Regular security assessments and endpoint monitoring can help detect suspicious activity indicative of exploitation attempts. Finally, organizations should maintain up-to-date inventories of affected devices and ensure timely communication with users regarding security updates.

Description

Improper handling of insufficient permissions or privileges in Samsung Account prior to version 15.5.00.18 allows local attackers to access data in Samsung Account. User interaction is required for triggering this vulnerability.

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality of sensitive user data stored in Samsung Account on mobile devices. Organizations with employees using Samsung mobile devices for corporate communication or data synchronization could face data leakage risks if an attacker gains local access to these devices. This could lead to exposure of personal identifiable information (PII), corporate credentials, or other sensitive data, potentially facilitating further attacks such as identity theft or unauthorized access to corporate resources. Although the vulnerability does not impact data integrity or device availability, the confidentiality breach alone can have regulatory implications under GDPR and other data protection laws in Europe. The requirement for local access and user interaction limits the attack scope but does not eliminate risk, especially in environments where devices may be lost, stolen, or accessed by unauthorized personnel. The absence of known exploits reduces immediate threat but does not preclude future exploitation once details become widely known.

CWE-280Improper Handling of Insufficient Permissions or Privileges (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Always check to see if you have successfully accessed a resource or system functionality, and use proper error handling if it is unsuccessful. Do this even when you are operating in a highly privileged mode, because errors or environmental conditions might still cause a failure.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2025, 07:14 UTC

WeaknessesCWE-280

Technical details

References

Community reviews

Related threats