dbcve.org
Android Usb DriverApplication · Samsung

CVE-2026-21038

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 1.9.5.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper input validation in Samsung Android USB Driver for Windows prior to version 1.9.5.0 allows local attacker to access out-of-bounds memory.

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 confidence

This vulnerability exists in Samsung Android USB Driver for Windows versions prior to 1.9.5.0. Improper input validation allows a local attacker to access out-of-bounds memory, potentially leading to information disclosure or code execution within the context of the driver.

MitigationUpdate Samsung Android USB Driver for Windows to version 1.9.5.0 or later to address the input validation flaw.

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
Android Usb DriverApplication
Affected:< 1.9.5.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Samsung Android USB Driver is installed
    Open Control Panel > Programs and Features, or Device Manager > Universal Serial Bus controllers, and look for entries named 'Samsung Android USB Driver' or similar Samsung USB driver components.
    Affected if The driver is not listed in Programs and Features or Device Manager.
  2. Locate the driver executable files
    Navigate to the Samsung USB Driver installation directory. Common paths: C:\Program Files\Samsung\Samsung Android USB Driver\ or C:\Program Files (x86)\Samsung\Samsung Android USB Driver\. Identify the main driver file (typically SecUSB.sys, SAMSUNG USB Driver.exe, or similar .sys/.exe files in the driver folder.
    Affected if No Samsung driver files are found in the expected installation directories.
  3. Check the installed driver version
    Right-click on the primary driver executable or .sys file, select Properties, then go to the Details tab. Look for 'File version' or 'Product version' field. Record the version number shown.
    Affected if The version displayed is missing or cannot be determined.
  4. Compare version against vulnerable range
    Compare the obtained version number to the affected range: any version prior to 1.9.5.0 is vulnerable. For example, versions like 1.9.4.0, 1.9.3.0, 1.8.x, etc. would be affected. Versions 1.9.5.0 and later are not vulnerable.
    Affected if The installed version is a four-part number where the first three parts (e.g., 1.9.4) are less than 1.9.5, or the version cannot be verified as 1.9.5.0 or higher.

A user is affected if Samsung Android USB Driver for Windows is installed with a version number lower than 1.9.5.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.9.5.0 or later
Fixed in 1.9.5.0
Interim mitigation

Update Samsung Android USB Driver for Windows to version 1.9.5.0 or later to address the input validation flaw.

Recommended fix High confidence

Samsung Android USB Driver version 1.9.5.0

  1. Identify the current version of Samsung Android USB Driver installed on the Windows system
  2. Navigate to the official Samsung security website (security.samsungmobile.com) or Samsung support portal
  3. Download Samsung Android USB Driver version 1.9.5.0 or later
  4. Uninstall the current version of the Samsung Android USB Driver through Windows Control Panel or Settings
  5. Restart the Windows system
  6. Install the newly downloaded version 1.9.5.0 or later
  7. Restart the system again to ensure driver proper installation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Usb Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21038 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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