dbcve.org
Galaxy WearableApplication · Samsung

CVE-2026-21013

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-13
Fix available
A fix is available. Upgrade to 2.2.68.26 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
Incorrect default permission in Galaxy Wearable prior to version 2.2.68.26 allows local attackers to access sensitive 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 confidence

Galaxy Wearable Android application prior to version 2.2.68.26 ships with incorrect default file system or data permissions that allow any local user or malicious app on the same device to read sensitive application data, configuration, or stored credentials without elevated privileges.

MitigationUpdate Galaxy Wearable to version 2.2.68.26 or later via the Galaxy Store or Google Play Store to obtain the corrected permission settings.

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 WearableApplication
Affected:< 2.2.68.26

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. Check if Galaxy Wearable app is installed and get its version
    Run 'adb shell pm list packages' to find the Galaxy Wearable package name, then run 'adb shell dumpsys package <package_name> | grep versionName' to retrieve the installed version. Common package names include com.samsung.android.galaxywearable or com.samsung.android.app.watchmanager.
    Affected if The installed version is lower than 2.2.68.26
  2. Verify the app version via app settings UI
    On the Android device, go to Settings > Apps > Galaxy Wearable (or Watch Manager) > App info to view the version number.
    Affected if The displayed version is lower than 2.2.68.26
  3. Inspect file permissions on the app's data directory
    Run 'adb shell ls -la /data/data/<package_name>' (replacing <package_name> with the actual Galaxy Wearable package name found in step 1) to examine the directory permissions.
    Affected if The data directory permissions allow access by other apps or users (for example, permissions are set to 755 or 777 instead of the more restrictive 700 or 750)
  4. Check for sensitive files in the app's shared preferences or databases
    Run 'adb shell run-as <package_name> ls -la files/' and 'adb shell run-as <package_name> ls -la shared_prefs/' to list files inside the app's private directory.
    Affected if These commands succeed without permission errors, indicating other processes can access the app's private data (vulnerable)

You are affected if Galaxy Wearable version is below 2.2.68.26 and the app's data directory permissions are too permissive, allowing unauthorized access to sensitive application data.

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

Update Galaxy Wearable to version 2.2.68.26 or later via the Galaxy Store or Google Play Store to obtain the corrected permission settings.

Recommended fix High confidence

2.2.68.26 or later

  1. Open Google Play Store or Samsung Galaxy Store on the device
  2. Search for "Galaxy Wearable"
  3. Tap Update to install version 2.2.68.26 or later
  4. Alternatively, open the Galaxy Wearable app, go to Settings > About Galaxy Wearable > Check for updates
  5. Verify the updated version by checking Settings > About Galaxy Wearable
Caveat Security patch升级 usually has minimal risk; however, ensure device compatibility before updating

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

Fix this in Galaxy Wearable Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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