dbcve.org
Galaxy StoreApplication · Samsung

CVE-2026-21002

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
Improper verification of cryptographic signature in Galaxy Store prior to version 4.6.03.8 allows local attacker to install arbitrary application.

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 confidence

Galaxy Store versions prior to 4.6.03.8 contain improper cryptographic signature verification, allowing a local attacker to bypass the app signing validation and install arbitrary applications without proper trusted signatures.

MitigationUpdate Galaxy Store to version 4.6.03.8 or later. For enterprise environments, ensure mobile device management policies enforce the update and restrict side-loading to prevent exploitation.

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. Check Galaxy Store app version
    On the Samsung device, go to Settings > Apps > Galaxy Store > App info, or use ADB command: `adb shell dumpsys package com.sec.android.app.samsungapps | grep versionName`
    Affected if The displayed version is lower than 4.6.03.8 (e.g., 4.6.00.5, 4.5.12.3, etc.)
  2. Verify installation from unknown sources setting
    On the device, go to Settings > Security and privacy > Install unknown apps, or Settings > Apps > Special access > Install unknown apps. Check if Galaxy Store or other app sources are allowed to install apps.
    Affected if Installation from unknown sources is enabled for any app, allowing the bypass of signature validation
  3. Confirm device is not enterprise-managed
    Check Settings > About phone > Device status, or look for MDM/EMM profile indicators in Settings. On enterprise-managed devices, check if the organization enforces restrictions on app installations.
    Affected if The device is not managed by an MDM/EMM solution that restricts side-loading or enforces Galaxy Store updates
  4. Check for recent Galaxy Store updates
    Open Galaxy Store > Menu (three lines) > Settings > About Galaxy Store, or check the Galaxy Store app store page for the current available version.
    Affected if The store shows an available update to version 4.6.03.8 or later, indicating the installed version is outdated

The device is affected if Galaxy Store version is below 4.6.03.8 AND the device allows installation from unknown sources or is not enterprise-managed with enforced update policies.

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

Update Galaxy Store to version 4.6.03.8 or later. For enterprise environments, ensure mobile device management policies enforce the update and restrict side-loading to prevent exploitation.

Recommended fix High confidence

Galaxy Store version 4.6.03.8 or later

  1. Open the Galaxy Store app on your Samsung device
  2. Tap the menu icon (three lines) or navigate to Settings
  3. Look for 'Galaxy Store version' or check for updates within the app
  4. If an update is available, download and install version 4.6.03.8 or later
  5. Alternatively, ensure your device has the latest Samsung system updates installed, as Galaxy Store updates may be delivered through system software updates

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

Fix this in Galaxy Store Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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