Skip to main content

Android CVE-2026-20990

| EUVDEUVD-2026-12297 HIGH
2026-03-16 SamsungMobile
8.1
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as local user
  2. Exploit
    Export unprotected Secure Folder component
  3. Impact
    Launch arbitrary activity with Secure Folder privileges

Vulnerability Assessment

Exploitation Conditions

Local authentication required. Vulnerable Secure Folder versions prior to SMR Mar-2026 Release 1 with improper component export protection. Attacker must have local user account access to device.

Impact

Despite the high CVSS 4.0 score of 8.4, the real-world risk appears moderate based on several factors. The local attack vector (AV:L) requires an attacker to have already compromised the device or convince a user to install malicious software, and low privileges (PR:L) are still required. The lack of KEV listing indicates no known active exploitation, and the absence of EPSS data suggests limited exploitation probability. The high confidentiality (VC:H) and integrity (VI:H) impact scores reflect the sensitivity of data protected by Secure Folder, making this a priority for organizations using Samsung devices with sensitive data, but not an emergency patch scenario given the local access requirement and no evidence of wild exploitation.

Exploit ScenarioDerived

An attacker would need to convince a user to install a malicious application on their Samsung device, which would then exploit the improperly exported components in Secure Folder to launch activities with elevated privileges, potentially accessing or modifying protected data within the secure container. The attack requires no user interaction after the malicious app is installed, as indicated by the UI:N in the CVSS vector, making it particularly dangerous once the initial foothold is established. No public proof-of-concept exists for this vulnerability at this time.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 16, 2026

Google's Secure Folder prior to the March 2026 SMR release improperly exports Android application components, enabling local attackers to execute arbitrary activities with Secure Folder privileges. This high-severity vulnerability affects users with local device access and could allow privilege escalation or unauthorized access to protected data. No patch is currently available.

Earlier versions of this analysis (1)
v1 Mar 16, 2026 - 05:00 CVSS 8.1

A vulnerability in Samsung Secure Folder allows local attackers with low privileges to launch arbitrary activities with elevated Secure Folder privileges due to improperly exported Android application components. This vulnerability affects Secure Folder versions prior to SMR March-2026 Release 1 and has a high CVSS score of 8.4, though it requires local access and some user privileges to exploit. No evidence of active exploitation exists (not in KEV), and the EPSS score is not available, suggesting limited real-world exploitation activity.

RemediationAI

Update Samsung Secure Folder to SMR March-2026 Release 1 or later through the standard Samsung security update process via Settings > Software update > Download and install. Samsung typically delivers these updates as part of their monthly security maintenance releases. Until the update can be applied, users should limit the installation of untrusted applications and avoid granting unnecessary permissions to apps, as exploitation requires a malicious local application to be present on the device.

Affected VersionsENISA

Samsung Mobile Devices patch: SMR Mar-2026 Release in Android 14, 15, 16

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Samsung Secure Folder is a security application that creates an isolated, encrypted space on Samsung devices to store sensitive apps and data separately from the main device environment. The vulnerability stems from improperly exported Android application components, which occurs when Android activities, services, or broadcast receivers are inadvertently made accessible to other applications without proper access controls. While no specific CWE is assigned, this type of vulnerability typically falls under component exposure issues common in Android applications where exported components can be invoked by malicious apps to perform unauthorized actions with the privileges of the vulnerable application.

Know when Android gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

Improper export of android application components in Secure Folder prior to SMR Mar-2026 Release 1 allows local attackers to launch arbitrary activity with Secure Folder privilege.

Executive ViewAI

Why It Matters

A high-severity vulnerability in Samsung Secure Folder could allow attackers with local device access to bypass security controls and access sensitive data stored in the encrypted container. This poses significant risk to organizations using Samsung devices for sensitive information storage, particularly for BYOD programs or shared devices, though exploitation requires local presence and user-level access.

Business Impact: High
Compensating Controls

Disable Secure Folder on BYOD devices and shared devices where possible; enforce device-level encryption via Knox platform; implement mobile device management (MDM) to restrict app installation and enforce strong authentication; segment networks to limit local attack surface; educate users to avoid storing highly sensitive data in Secure Folder until patched; monitor device logs for suspicious Secure Folder activity; consider alternative secure storage solutions for sensitive data pending patch availability.

Threat Intelligence Overview

EPSS Score
0.0%
Top 98% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in Samsung SMR Mar-2026 Component Security

View all 2
CVE-2015-3105 CRITICAL POC
10.0 Jun 10

Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy