Skip to main content

Samsung Assistant CVE-2026-21033

| EUVDEUVD-2026-34805 MEDIUM
2026-06-05 SamsungMobile GHSA-24v9-59pc-wmrv
6.9
CVSS 4.0 · Vendor: SamsungMobile
View

Attack ChainAIDerived

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

  1. Access
    Install malicious app on target Android device
  2. Delivery
    Send crafted intent to exported ExpressHomeWidgetReceiver
  3. Exploit
    Bypass missing component permission enforcement
  4. Execution
    Trigger arbitrary script execution in Samsung Assistant context
  5. Impact
    Exfiltrate confidential data accessible to the assistant

Vulnerability Assessment

Exploitation Conditions

Local access to the Android device is required - specifically, the ability to execute code on the device, most realistically via a malicious application installed from an untrusted source (sideloaded APK, third-party app store). The CVSS 4.0 vector (PR:N, UI:N) confirms no special OS-level privileges or victim interaction are needed once the malicious app is installed. The vulnerable condition is the presence of Samsung Assistant prior to version 9.3.14 with its ExpressHomeWidgetReceiver component improperly exported without adequate permission enforcement. Exploitation is strictly bounded by the local attack vector (AV:L) - remote unauthenticated exploitation over a network is not possible. Limitations on exploitation include: the attacker must achieve local code execution on the target device (a non-trivial prerequisite for targeted attacks), the impact is limited to confidentiality (no integrity or availability impact per CVSS), and the vulnerability does not affect the underlying Android OS or other applications.

Impact

The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N) confirms local attack vector with low complexity, no required privileges, no user interaction, and high confidentiality impact on the vulnerable component. Crucially, the local attack vector caps real-world blast radius to on-device threats - remote network exploitation is not feasible under this vector. The 'Information Disclosure' tag aligns with the VC:H / VI:N / VA:N impact profile, suggesting the primary risk is unauthorized access to data rather than device takeover or availability disruption. No EPSS score is available in the provided data. The CVE is not listed in CISA KEV, and no POC has been identified. Taken together, this represents a moderate-priority issue: meaningful for organizations managing large Android device fleets with strict data-handling requirements (e.g., enterprise MDM environments), but lower urgency than network-exploitable vulnerabilities for typical consumer users who do not sideload untrusted applications.

Exploit ScenarioDerived

An attacker distributes a malicious Android application - either through a third-party app store or via sideloading - onto a device running Samsung Assistant prior to 9.3.14. Once installed, the malicious app sends a specially crafted intent directly to the improperly exported ExpressHomeWidgetReceiver component, bypassing access control checks. This triggers execution of an arbitrary script within Samsung Assistant's context, exposing confidential data accessible to the assistant. No public POC has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 – Jun 05, 2026

Improper export of the ExpressHomeWidgetReceiver Android component in Samsung Assistant (prior to version 9.3.14) enables a local attacker without special privileges to send crafted intents to the exposed receiver and execute arbitrary scripts on the device. The CVSS 4.0 score of 6.9 reflects high confidentiality impact (VC:H) with a local attack vector - an on-device malicious application is a realistic threat model. No public exploit has been identified and this CVE does not appear in CISA KEV at time of analysis.

RemediationAI

The primary fix is to update Samsung Assistant to version 9.3.14 or later, as confirmed by the Samsung Mobile Security June 2026 advisory at https://security.samsungmobile.com/serviceWeb.smsb?year=2026&month=06. Updates are typically delivered via the Galaxy Store or Samsung Software Update mechanism on affected devices. As a compensating control on devices that cannot be immediately updated, administrators managing enterprise Android fleets via MDM should enforce app allowlisting policies to prevent untrusted third-party applications from being installed - this directly removes the threat actor's necessary foothold, since exploitation requires a malicious app running locally on the device. Restricting sideloading (disabling 'Install unknown apps' in Android settings) reduces the attack surface further, though it does not eliminate risk from apps distributed via the Play Store. Note that these compensating controls impose usability restrictions and do not address the underlying component export flaw.

Affected VersionsENISA

Samsung Assistant patch: 9.3.14

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 Assistant is a Samsung-developed AI assistant application for Android devices, identified by CPE cpe:2.3:a:samsung_mobile:samsung_assistant:*:*:*:*:*:*:*:*. The vulnerability resides in ExpressHomeWidgetReceiver, an Android BroadcastReceiver component. In Android, application components such as BroadcastReceivers can be declared as exported in the AndroidManifest.xml, making them reachable by other applications on the same device. When exported without enforcing custom permissions or intent filters with adequate restrictions, any local application can send arbitrary intents to the component. This class of vulnerability is characteristic of improper Android component export patterns - conceptually aligned with CWE-926 (Improper Export of Android Application Components) - though no formal CWE is assigned to this CVE. The 'Google' tag in the source intelligence likely reflects the Android platform context rather than a distinct Google product being affected.

Know when Samsung Assistant 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

Vendor (SamsungMobile) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (SamsungMobile) · only source for this CVE.

CVSS VectorVendor: SamsungMobile

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
CVSS changed
Jun 05, 2026 - 11:22 NVD
6.9 (MEDIUM)
CVE Published
Jun 05, 2026 - 10:15 nvd
UNKNOWN (no severity yet)
CVE Published
Jun 05, 2026 - 10:15 nvd
MEDIUM 6.9

DescriptionCVE.org

Improper export of android application components in ExpressHomeWidgetReceiver of Samsung Assistant prior to version 9.3.14 allows local attacker to execute arbitrary script.

Threat Intelligence Overview

EPSS Score
0.0%
Top 97% exploitable
Data Quality
6 sources
Confidence: High

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
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.

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