CVE-2025-20939
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 · uneditedImproper authorization in wireless download protocol in Galaxy Watch prior to SMR Apr-2025 Release 1 allows physical attackers to update device unique identifier of Watch devices.
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 confidenceImproper authorization in the wireless download protocol of Samsung Galaxy Watch devices allows a physical attacker with proximity to modify the device's unique identifier. This vulnerability exists prior to the SMR Apr-2025 Release 1 patch.
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= 5.0CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device modelCheck if the device is a Samsung Galaxy Watch model. Look at device settings or packaging for the model name.Affected if The device is not a Samsung Galaxy Watch (not affected)
-
Check Wear OS versionNavigate to Settings > About Watch > Software Information on the Galaxy Watch and verify the Wear OS version.Affected if Wear OS version is exactly 5.0 (potentially affected if SMR is also before Apr-2025 Release 1)
-
Check SMR versionNavigate to Settings > About Watch > Software Information and check the SMR (Samsung Maintenance Release) version number.Affected if SMR version is before Apr-2025 Release 1 (vulnerable to this CVE)
A user is affected if they have a Samsung Galaxy Watch running Wear OS version 5.0 with an SMR version earlier than the Apr-2025 Release 1 patch.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Galaxy Watch devices to SMR Apr-2025 Release 1 or later to remediate this vulnerability.
SMR Apr-2025 Release 1
- On the Galaxy Watch, open the Settings app
- Scroll down and select 'Watch settings' or 'About watch'
- Tap on 'Software update'
- Select 'Download and install' to check for the SMR Apr-2025 Release 1 update
- Ensure the watch is connected to a stable Wi-Fi network and placed on its charger during the update process
- After the update completes, verify the software version reflects SMR Apr-2025 Release 1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20939 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20939 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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