CVE-2025-21059
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 Samsung Health prior to version 6.30.5.105 allows local attackers to access data in Samsung Health.
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 confidenceThis is an improper authorization (broken access control) vulnerability in Samsung Health Android app. The flaw allows a local attacker—someone with physical access to the device or able to execute code locally—to bypass authorization checks and access sensitive health data stored within the app. The vulnerability affects versions prior to 6.30.5.105.
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< 6.30.5.105CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Samsung Health version via Android SettingsGo to Settings > Apps > Samsung Health > App info, then locate the Version field showing the package versionAffected if The displayed version number is less than 6.30.5.105 (for example, 6.30.5.100, 6.29.x, or earlier)
-
Check installed Samsung Health version via adb commandRun 'adb shell pm list packages | grep samsung.health' followed by 'adb shell dumpsys package <package_name> | grep versionName' to retrieve the exact version stringAffected if The versionName output is lower than 6.30.5.105
-
Check version within the Samsung Health appOpen Samsung Health app, tap the profile icon or menu, navigate to About Samsung Health or Settings > About, and note the displayed versionAffected if The reported version is below 6.30.5.105
A device is affected if Samsung Health is installed with any version lower than 6.30.5.105, making it vulnerable to local authorization bypass for health data access.
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 · scoped6.30.5.105
Update Samsung Health to version 6.30.5.105 or later via the Galaxy Store or Google Play Store to remediate the authorization bypass.
Samsung Health version 6.30.5.105 or later
- Open the Galaxy Store app on your Samsung device
- Search for 'Samsung Health'
- If an update is available, tap 'Update' to install version 6.30.5.105 or later
- Alternatively, open Google Play Store, search for Samsung Health, and update if a newer version is available
- Verify the installed version by opening Samsung Health > Settings > About Samsung Health
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21059 — 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-21059 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