CVE-2026-20993
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 Samsung Assistant prior to version 9.3.10.7 allows local attacker to access saved information.
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 · moderate confidenceImproper export of Android application components in Samsung Assistant versions prior to 9.3.10.7 allows a local attacker to access saved information through improperly exposed application components.
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.10.7CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify installed Samsung Assistant versionOn the Android device, go to Settings > Apps > Samsung Assistant, or use ADB command: adb shell dumpsys package com.samsung.android.app.assistant | grep versionNameAffected if The displayed version is lower than 9.3.10.7 or the version cannot be determined (app may be hidden or disabled)
-
Verify component export configurationUse ADB to inspect the app manifest: adb shell dumpsys package com.samsung.android.app.assistant | grep -i "exported" to check if components are marked as exportedAffected if Any sensitive components (activities, services, broadcast receivers) are found with exported="true" and no proper permission protection
-
Confirm app is present and activeCheck if Samsung Assistant is installed and enabled: adb shell pm list packages | grep assistantAffected if The package exists on the device (indicating the app is installed and potentially vulnerable if version is below 9.3.10.7)
A user is affected if Samsung Assistant version is installed and is lower than 9.3.10.7, making the improperly exported application components accessible to local attackers.
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.10.7
Upgrade Samsung Assistant to version 9.3.10.7 or later to address the improper component export vulnerability.
9.3.10.7 or later
- Open Samsung Galaxy Store or Google Play Store on your Samsung device
- Search for "Samsung Assistant" or "Bixby" (depending on the exact app name)
- Check the current installed version in app settings
- Update the app to version 9.3.10.7 or later
- Verify the update was successful by checking the app version in Settings > Apps > Assistant
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20993 — 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-20993 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