CVE-2025-21004
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 verification of intent by broadcast receiver in System UI for Galaxy Watch prior to SMR Jul-2025 Release 1 allows local attackers to power off the device.
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 confidenceA broadcast receiver in the System UI for Samsung Galaxy Watch fails to properly verify the intent of incoming broadcasts, allowing a local attacker to send a crafted broadcast that triggers an unintended device power-off.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify device modelCheck if the device is a Samsung Galaxy Watch by going to Settings > About Watch > Model Name or checking the device packaging/listingAffected if Device is not a Samsung Galaxy Watch (different manufacturers are not affected)
-
Check Wear OS versionNavigate to Settings > About Watch > Software Version or Settings > System > Software Version to find the Wear OS release numberAffected if Version is exactly 5.0 (only this specific version is listed as affected)
-
Verify current security patch levelGo to Settings > About Watch > Software Version > Security Patch Level to see the installed SMR (Samsung Maintenance Release) dateAffected if Security patch level is before July 2025 (the fix was released in SMR Jul-2025 Release 1)
-
Check for unauthorized broadcastsMonitor device logs via adb logcat or Lookout/Malwarebytes for Android for unusual broadcast messages targeting system components, particularly those referencing power-off or shutdown intentsAffected if Unexpected broadcast intents targeting System UI or power management are observed
Device is affected if it is a Samsung Galaxy Watch running Wear OS version 5.0 with a security patch level earlier than July 2025.
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 · scopedApply the SMR Jul-2025 Release 1 or later security update for Galaxy Watch devices to remediate this vulnerability.
SMR Jul-2025 Release 1
- Check the current Galaxy Watch System UI version in Settings > About Watch > Software version
- Navigate to Settings > Software Update on the Galaxy Watch or use the Galaxy Wearable app on the connected phone
- Ensure the watch is connected to Wi-Fi and has sufficient battery (above 50%)
- Check for and install the SMR Jul-2025 Release 1 update which contains the security patch for CVE-2025-21004
- After update completion, verify the System UI has been updated to the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21004 — 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-21004 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