AndroidOperating system · Samsung

CVE-2025-21010

MEDIUM · 6.0 CVSS v3.1 Published 2025-08-06

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Zero-click

Official description

NVD · unedited

Improper privilege management in SamsungAccount prior to SMR Aug-2025 Release 1 allows local privileged attackers to deactivate Samsung account.

Technical summary

dbcve analysis · moderate confidence

This is a local privilege escalation vulnerability in SamsungAccount where improper authorization checks allow a locally privileged attacker to deactivate Samsung user accounts. The vulnerability exists in versions prior to the SMR Aug-2025 Release 1 patch, exploiting insufficient validation of privilege escalation requests within the account management subsystem.

MitigationApply Samsung SMR Aug-2025 Release 1 or later to receive the patched SamsungAccount version; enforce MDM policies to ensure devices remain updated.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

AndroidOperating system

Affected:= 13.0= 14.0= 15.0= 16.0

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: High
User interaction: None
Scope: Changed
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check the Android version on the device

Go to Settings > About Phone > Android version, or run `getprop ro.build.version.release` via ADB

Affected if The device is running Android 13.0, 14.0, 15.0, or 16.0 and has not received the SMR Aug-2025 Release 1 patch
Verify SamsungAccount app is installed

Go to Settings > Apps > SamsungAccount, or run `pm list packages | grep samsungaccount` via ADB

Affected if The SamsungAccount application is present on the device
Check the SamsungAccount app version

Go to Settings > Apps > SamsungAccount > App version, or run `dumpsys package com.samsung.android.account` via ADB to read the versionName and versionCode

Affected if The installed SamsungAccount version is earlier than the version included in SMR Aug-2025 Release 1 - compare your version against the patched release
Confirm if the SMR Aug-2025 Release 1 patch has been applied

Go to Settings > About Phone > Software information > Build number, or run `getprop ro.build.version.sem` via ADB to check the Samsung Maintenance Release (SMR) version

Affected if The SMR version is earlier than Aug-2025 Release 1 (format typically shows as SMRx-xxxx)

A user is affected if their device runs Android 13.0-16.0 with SamsungAccount installed, and the device has not received the SMR Aug-2025 Release 1 patch that contains the fixed SamsungAccount version.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Samsung SMR Aug-2025 Release 1 or later to receive the patched SamsungAccount version; enforce MDM policies to ensure devices remain updated.

Recommended fix Moderate confidence

Samsung SMR Aug-2025 Release 1 (or later)

Check current Android version and security patch level on the device (Settings > About Phone > Software Information)
Check for and install the August 2025 Samsung Security Maintenance Release (SMR Aug-2025 Release 1) via Settings > Software Update > Download and Install
If automatic updates are enabled, ensure the device connects to Wi-Fi and is charging to receive the security update
After updating, verify the security patch level shows August 2025 or later in Settings > About Phone > Software Information > Security patch level

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

Fix this in Android Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing3.0 h
Review / QA1.0 h

7.0 hours of engineering $1,210

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

security.samsungmobile.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21010 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-21010?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 6.0 Medium

Exploit likelihood EPSS, next 30 days 0.1%

Affects: Android

Remediation

Need this fixed?

Fix this in Android 7 hrs · Low

Typical engagement from $1,210

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-21010 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References