Skip to main content
VulnerabilityPublished

CVE-2026-21001: Samsung Mobile Galaxy Store · Path Traversal

Affects Samsung Mobile Galaxy StoreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Samsung MobileGalaxy StoreAffected–Fixed in–

AI-suggested

To mitigate CVE-2026-21001, organizations and users should: 1) Update the Galaxy Store app to version 4.6.03.8 or later as soon as the patch is available from Samsung to eliminate the vulnerability. 2) Enforce strict local access controls on devices, including strong lock screens, biometric authentication, and device encryption to prevent unauthorized local access. 3) Limit physical access to devices and educate users on the risks of sharing devices or installing untrusted applications that could facilitate local exploitation. 4) Monitor device behavior for unusual file creation or modifications within the Galaxy Store directories, using mobile endpoint detection tools where feasible. 5) Employ mobile device management (MDM) solutions to enforce app updates and security policies centrally. 6) Consider disabling or restricting the Galaxy Store app in enterprise environments where alternative app distribution methods exist, reducing the attack surface. 7) Maintain regular backups of critical mobile data to recover from potential compromise. These steps go beyond generic advice by focusing on controlling local access, monitoring specific app behavior, and leveraging enterprise management tools.

Description

Path traversal in Galaxy Store prior to version 4.6.03.8 allows local attacker to create file with Galaxy Store privilege.

References

Community reviews

Loading reviews…