dbcve.org
MembersApplication · Samsung

CVE-2026-20986

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 15.5.05.4 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 Samsung Members prior to Chinese version 15.5.05.4 allows local attackers to overwrite data within Samsung Members.

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 the Samsung Members Chinese mobile application (versions prior to 15.5.04) allows a local attacker to escape the intended directory boundaries and overwrite files outside the application's intended storage area. This could allow modification of application data or configuration files.

MitigationUpdate Samsung Members to version 15.5.05.4 or later. Organizations should verify that all managed devices have applied the patched version.

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
MembersApplication
Affected:< 15.5.05.4

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. Confirm Samsung Members app is installed
    On the Android device, go to Settings > Apps > Samsung Members, or use ADB command: pm list packages | grep samsung.members
    Affected if The app is not installed, the vulnerability does not apply. If installed, continue to version check.
  2. Determine the installed version number
    In device Settings > Apps > Samsung Members > App info, note the Version number displayed. Alternatively, use ADB: dumpsys package com.samsung.android.三星生活家 | grep versionName
    Affected if No version number can be retrieved indicates the app may be installed but version cannot be confirmed.
  3. Compare version against vulnerable range
    Check if the installed version is below 15.5.05.4. Note: The CVE specifies versions prior to 15.5.05.4, but the affected products field shows < 15.5.05.4. Any version below 15.5.05.4 is in the vulnerable range.
    Affected if Installed version is 15.5.04 or lower indicates the device is running a vulnerable version.
  4. Verify the Chinese regional variant
    Confirm the app package name matches the Chinese variant (typically com.samsung.android.三星生活家 or similar Chinese regional package). Check via Settings > Apps or ADB: pm list packages
    Affected if The vulnerability specifically affects the Chinese mobile application version; non-Chinese variants may not be affected by this specific CVE.

The device is affected if Samsung Members (Chinese variant) is installed with a version lower than 15.5.05.4.

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

Update Samsung Members to version 15.5.05.4 or later. Organizations should verify that all managed devices have applied the patched version.

Recommended fix High confidence

15.5.05.4 (Chinese version)

  1. Open Samsung Members application on the device
  2. Navigate to Settings or About section within the app
  3. Check the current application version to confirm it is below 15.5.05.4
  4. Open Samsung Galaxy Store or device app store
  5. Search for Samsung Members and update to version 15.5.05.4 or later
  6. Verify the updated version number after installation completes

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

Fix this in Members Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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