VulnerabilityPublished 5 Nov 2025

CVE-2025-21077: Samsung Email · Improper Input Validation

Source GCVE Database

Compare

Authoritative record:CVE-2025-21077· Low 3.3

Not known to be exploited · CVSS 3.3 Low · fixed in 6.2.06.0 : update Samsung Email when convenient.

Data as of 4 Nov 2026, 18:03 UTC

CVSS 3.1 base score

3.3Low

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

Affects: Samsung Email prior to 6.2.06.0
Patch: Available – fixed in 6.2.06.0

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
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: 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: 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 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 4 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-r4jr-4jcc-p7qg

What to do

AI-suggested

A fix is available in Samsung Email version 6.2.06.0. Users and administrators should update to version 6.2.06.0 or later to remediate this vulnerability.

Description

CVE-2025-21077 is a vulnerability in Samsung Email versions prior to 6.2.06.0 caused by improper input validation. This flaw allows local attackers to launch arbitrary activities with the privileges of the Samsung Email application. The vulnerability has a low severity rating and does not impact confidentiality, integrity, or availability beyond limited local activity launch.

Impact

The impact is limited to local attackers being able to launch arbitrary activities with Samsung Email privileges. There is a low confidentiality impact and no integrity or availability impact. This does not allow remote exploitation or broader system compromise based on the provided data.

Summary

An improper input validation vulnerability exists in Samsung Email before version 6.2.06.0. Local attackers can exploit this flaw to launch arbitrary activities within the Samsung Email app context, potentially leveraging the app's privileges. The CVSS 3.1 base score is 3.3, reflecting low impact with local attack vector, low complexity, and no user interaction required. No known exploits are reported in the wild, and the vulnerability is limited to local privilege escalation within the app.

References

Community reviews

Loading reviews…