VYPR
Unrated severityNVD Advisory· Published Feb 4, 2025· Updated Feb 12, 2025

CVE-2025-20894

CVE-2025-20894

Description

Improper access control in Samsung Email prior to 6.1.97.1 lets physical attackers access data across multiple user profiles.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Improper access control in Samsung Email prior to 6.1.97.1 lets physical attackers access data across multiple user profiles.

Vulnerability

Samsung Email versions prior to 6.1.97.1 contain an improper access control vulnerability that allows a physical attacker to access data across multiple user profiles. The flaw exists in the application's handling of user profile boundaries, enabling data leakage between profiles without proper authentication.

Exploitation

To exploit this vulnerability, an attacker must have physical access to a device running an affected version of Samsung Email. No special authentication or user interaction beyond that required to unlock the device is necessary. The attacker can navigate the application to access data belonging to other user profiles on the same device.

Impact

Successful exploitation results in unauthorized disclosure of data from multiple user profiles. The attacker gains access to sensitive information that is intended to be isolated between profiles, leading to a breach of confidentiality and violating user profile separation.

Mitigation

Users should update Samsung Email to version 6.1.97.1 or later, which contains the fix. The update was released in January 2025 as part of Samsung's monthly security maintenance release. No workarounds are documented in the available references [1].

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.