dbcve.org
Galaxy StoreApplication · Samsung

CVE-2026-21001

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 4.6.03.8 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
Path traversal in Galaxy Store prior to version 4.6.03.8 allows local attacker to create file with Galaxy Store privilege.

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

A path traversal vulnerability in Samsung Galaxy Store versions prior to 4.6.03.8 allows a local attacker to write files to arbitrary filesystem locations by manipulating file paths in Galaxy Store operations. The attacker exploits insufficient path validation to create files with the elevated privileges assigned to the Galaxy Store application.

MitigationUpgrade Galaxy Store to version 4.6.03.8 or later, which contains proper path traversal protection. If upgrading is not immediately possible, restrict the Galaxy Store application's file write permissions and monitor for suspicious file creation activity.

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
Galaxy StoreApplication
Affected:< 4.6.03.8

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checks

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

  1. Identify Galaxy Store package name
    Run 'adb shell pm list packages | grep -i galaxy' to find the Samsung Galaxy Store package name (typically 'com.sec.android.app.samsungapps' or 'com.samsung.android.app.samsungapps')
    Affected if Package is not found - Galaxy Store may not be installed or uses a different package name
  2. Retrieve installed Galaxy Store version
    Run 'adb shell dumpsys package <package_name>' and look for versionName and versionCode in the output, or check via Settings > Apps > Galaxy Store > App info on the device
    Affected if Version retrieved is less than 4.6.03.8 (for example, 4.6.03.7, 4.5.x.x, etc.)
  3. Verify path traversal attack surface exists
    Check if Galaxy Store has write permissions to external storage or internal app directories by reviewing app permissions via 'adb shell dumpsys package <package_name>' and looking for WRITE_EXTERNAL_STORAGE or similar write permissions
    Affected if Galaxy Store has broad file write permissions and version is below 4.6.03.8
  4. Monitor for suspicious file creation activity
    Review device logs via 'adb logcat' filtering for Galaxy Store package name and look for unexpected file write operations to locations outside the app's private directory (paths containing ../ or absolute paths outside /data/data/<package_name>)
    Affected if Log entries show file writes to unexpected directories from Galaxy Store process

The device is affected if Samsung Galaxy Store is installed with a version number lower than 4.6.03.8, as this version range contains the vulnerable path traversal code.

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 4.6.03.8 or later
Fixed in 4.6.03.8
Interim mitigation

Upgrade Galaxy Store to version 4.6.03.8 or later, which contains proper path traversal protection. If upgrading is not immediately possible, restrict the Galaxy Store application's file write permissions and monitor for suspicious file creation activity.

Recommended fix High confidence

Galaxy Store version 4.6.03.8

  1. Open the Galaxy Store app on your Samsung device
  2. Tap the menu (three lines) in the top-left corner
  3. Select 'My Apps' to view available updates
  4. Locate 'Galaxy Store' in the list of apps with updates
  5. Tap 'Update' to install version 4.6.03.8 or later
  6. Alternatively, check for system updates in Settings > Software update to ensure your device firmware includes the Galaxy Store security patch

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

Fix this in Galaxy Store Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21001 — 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-21001 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