CVE-2025-21036VulnerabilityPublished 3 Sep 2025

CVE-2025-21036: Samsung Notes · Use of Implicit Intent for Sensitive Communication

Affects Samsung NotesSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium : upgrade to 4.4.30.63 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.4.30.63

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 3 Sep 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

Upgrade Samsung Notes to 4.4.30.63.

Affected software

Product	Affected	Fixed in
Samsung Mobile Samsung Notes	Affected <4.4.30.63	Fixed in 4.4.30.63

AI-suggested

1. Immediate update of Samsung Notes to version 4.4.30.63 or later on all Samsung mobile devices used within the organization to ensure the vulnerability is patched. 2. Implement mobile device management (MDM) solutions to enforce application updates and control app permissions, limiting the ability of unauthorized apps to gain local privileges or intercept intents. 3. Educate users about the risks of interacting with suspicious prompts or links that could trigger the vulnerability, emphasizing cautious behavior regarding app interactions and downloads. 4. Restrict local privilege escalation by enforcing strong device security policies, including secure lock screens, biometric authentication, and disabling developer options or USB debugging on corporate devices. 5. Monitor device logs and behavior for signs of privilege escalation or unusual access patterns to note files, enabling early detection of exploitation attempts. 6. Consider encrypting sensitive notes or using alternative secure note-taking applications with stronger access controls for highly sensitive information. 7. Regularly audit and review installed applications and permissions on corporate mobile devices to minimize the attack surface.

Description

Improper access control in Samsung Notes prior to version 4.4.30.63 allows local privileged attackers to access exported note files. User interaction is required for triggering this vulnerability.

Impact

For European organizations, the impact of this vulnerability can be significant, especially for those whose employees use Samsung mobile devices for work-related note-taking and data storage. The exposure of sensitive notes could lead to unauthorized disclosure of confidential business information, intellectual property, or personal data, potentially violating GDPR requirements regarding data protection and privacy. Since the vulnerability requires local privileged access and user interaction, the risk is somewhat mitigated but still relevant in scenarios where devices are lost, stolen, or compromised by malware that gains local privileges. The confidentiality impact is high, as sensitive notes can be accessed without integrity or availability being affected. This could facilitate corporate espionage, data leaks, or insider threats. Organizations in sectors such as finance, healthcare, legal, and government, where sensitive information is frequently stored on mobile devices, are particularly at risk. Additionally, the lack of known exploits in the wild suggests that proactive patching and mitigation can effectively prevent exploitation. However, the widespread use of Samsung devices in Europe means that a large number of endpoints could be vulnerable if not updated promptly.

CWE-927Use of Implicit Intent for Sensitive Communication (opens in a new tab)
Variant weaknessOWASP Top 10 A04:2021: Insecure Design (opens in a new tab)
The Android application uses an implicit intent for transmitting sensitive data to other applications.
Implementation
If the application only requires communication with its own components, then the destination is always known, and an explicit intent could be used.
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/serviceWeb.smsb?year=2025&month=09 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Sep 2025, 06:34 UTC

WeaknessesCWE-927

Technical details

References

Community reviews

Related threats