CVE-2026-21032
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper export of android application components in SmartHomeWidgetReceiver of Samsung Assistant prior to version 9.3.14 allows local attacker to execute arbitrary script.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an improper export vulnerability in Samsung Assistant's SmartHomeWidgetReceiver broadcast receiver. The component is exported without proper access controls, allowing a local malicious application to send intents to this receiver and execute arbitrary scripts. This is a classic Android component export misconfiguration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.3.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Samsung Assistant is installedGo to Settings > Apps > Samsung Assistant, or use ADB command: adb shell pm list packages | grep -i assistantAffected if Samsung Assistant is not found in installed apps, then not affected
-
Determine installed version of Samsung AssistantIn Settings > Apps > Samsung Assistant > App info, note the version number displayed under the app name; or use ADB: adb shell dumpsys package <package_name> | grep versionNameAffected if Version shown is lower than 9.3.14, indicating a potentially vulnerable version
-
Inspect AndroidManifest.xml for SmartHomeWidgetReceiver export statusObtain the Samsung Assistant APK (via ADB backup or APK extraction tool), then use aapt or APK tool to dump AndroidManifest.xml and search for '<receiver android:name="SmartHomeWidgetReceiver"' and check if android:exported="true" is presentAffected if SmartHomeWidgetReceiver component exists with android:exported="true" or no android:exported attribute (defaulting to true) in versions below 9.3.14
A user is affected if Samsung Assistant version is below 9.3.14 and the SmartHomeWidgetReceiver broadcast receiver is exported in the app's manifest, allowing any local app to send intents to execute scripts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.3.14
Update Samsung Assistant to version 9.3.14 or later. If unable to update, apply android:exported="false" to SmartHomeWidgetReceiver in AndroidManifest.xml or add proper permission checks to restrict access.
Samsung Assistant 9.3.14
- Open the Google Play Store or Samsung Galaxy Store on the affected device
- Search for Samsung Assistant
- If an update is available, tap Update to install version 9.3.14 or later
- Alternatively, ensure automatic updates are enabled for Samsung Assistant to receive future security patches
- Verify the installed version by checking the app info in device settings to confirm version 9.3.14 or higher is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21032 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21032 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data