HealthApplication · Samsung

CVE-2025-21019

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-06
Fix available
A fix is available. Upgrade to 6.30.1.003 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
Improper authorization in Samsung Health prior to version 6.30.1.003 allows local attackers to access data in Samsung Health. User interaction is required for triggering this vulnerability.

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

Improper authorization in Samsung Health prior to version 6.30.1.003 allows local attackers to bypass access controls and read protected health data. The vulnerability requires user interaction to trigger, likely through a malicious action within the app's context.

MitigationUpdate Samsung Health to version 6.30.1.003 or later to obtain the authorization fix. Users should also exercise caution with untrusted links or inputs within the app.

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
HealthApplication
Affected:< 6.30.1.003

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Verify Samsung Health is installed
    Check the device's application list or settings for Samsung Health. On Android, go to Settings > Apps > Samsung Health. On Samsung devices, it may also appear in the Samsung folder or app drawer.
    Affected if Samsung Health is present on the device
  2. Find the installed Samsung Health version
    Navigate to the Samsung Health app info screen (Settings > Apps > Samsung Health) and locate the version number displayed under the app name or in the 'About' section.
    Affected if Version information cannot be located or the app is installed without a clear version display
  3. Compare version against the affected range
    Compare the installed version number to 6.30.1.003. Note that version comparison should treat '6.30.1.003' as the minimum secure version - any version older than this (e.g., 6.29.x, 6.28.x, etc.) is in the affected range.
    Affected if Installed version is less than 6.30.1.003 (e.g., 6.30.0.021, 6.29.5.300, etc.)
  4. Confirm the app has access to health data
    Open Samsung Health and check if any health data such as steps, heart rate, sleep records, workout logs, or other biometric information has been recorded or synced to the app.
    Affected if Protected health data exists within Samsung Health and the installed version is below 6.30.1.003

A user is affected if Samsung Health is installed with a version lower than 6.30.1.003 and contains stored health data accessible through the app.

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

Update Samsung Health to version 6.30.1.003 or later to obtain the authorization fix. Users should also exercise caution with untrusted links or inputs within the app.

Recommended fix High confidence

Samsung Health version 6.30.1.003

  1. Open the Galaxy Store app on your Samsung device
  2. Search for "Samsung Health" in the search bar
  3. Tap on Samsung Health in the search results
  4. Tap the "Update" button to install version 6.30.1.003 or later
  5. Alternatively, open the Google Play Store, search for Samsung Health, and update from there
  6. Verify the updated version by opening Samsung Health and checking the app info

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

Fix this in Health 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-2025-21019 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21019 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