Samsung Secure Folder sensitive information

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Samsung Secure Folder. The impacted element is an unknown function. The manipulation leads to sensitive information. This vulnerability is uniquely identified as CVE-2025-21041. Local access is required to approach this attack. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Samsung Secure Folder (version now known). It has been rated as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a sensitive information vulnerability. Using CWE to declare the problem leads to CWE-922. The product stores sensitive information without properly limiting read or write access by unauthorized actors. Impacted is confidentiality. The summary by CVE is:

Insecure Storage of Sensitive Information in Secure Folder prior to Android 16 allows local attackers to access sensitive information.

It is possible to read the advisory at security.samsungmobile.com. The identification of this vulnerability is CVE-2025-21041 since 11/06/2024. The exploitation is known to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-26636). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 5.0

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CNA Base Score: 6.2
CNA Vector (SamsungMobile): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Sensitive information
CWE: CWE-922 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Timelineinfo

11/06/2024 CVE reserved
09/03/2025 +300 days Advisory disclosed
09/03/2025 +0 days VulDB entry created
09/20/2025 +17 days VulDB entry last update

Sourcesinfo

Vendor: samsung.com

Advisory: security.samsungmobile.com
Status: Confirmed

CVE: CVE-2025-21041 (🔒)
GCVE (CVE): GCVE-0-2025-21041
GCVE (VulDB): GCVE-100-322307
EUVD: 🔒

Entryinfo

Created: 09/03/2025 10:13
Updated: 09/20/2025 18:38
Changes: 09/03/2025 10:13 (60), 09/20/2025 09:20 (11), 09/20/2025 18:38 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!