CVE-2025-21050
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 input validiation in Contacts prior to SMR Oct-2025 Release 1 allows local attackers to access data across multiple user profiles.
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 input validation in the Contacts application allows local attackers to bypass profile boundaries and access contact data belonging to other user profiles on the same device. This suggests the application fails to properly validate or sanitize input used to reference contact records, enabling cross-user data leakage.
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= 13.0= 14.0= 15.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
- 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.
-
Identify device manufacturer and modelGo to Settings > About Phone > Device name and manufacturer. Confirm it is a Samsung device.Affected if Device is not a Samsung Android device (vulnerability is Samsung-specific)
-
Check Android versionGo to Settings > About Phone > Android version. Note the exact version number displayed.Affected if Android version is exactly 13.0, 14.0, or 15.0 (only these exact versions are affected)
-
Confirm multiple user profiles existGo to Settings > Users and Accounts > Users. Check if more than one user profile is configured on the device.Affected if Multiple user profiles are present (attack targets cross-profile contact access)
-
Verify Contacts app is installedLocate the Contacts application in the app drawer or go to Settings > Apps > Contacts (or Contacts Storage). Confirm the app is present.Affected if Contacts application is installed and accessible to the user
-
Check Samsung SMR patch levelGo to Settings > About Phone > Software Information > Security patch level. Note the date displayed.Affected if Security patch level is earlier than October 2025 (unpatched devices)
Device is affected if it is a Samsung Android device running exactly version 13.0, 14.0, or 15.0, has multiple user profiles configured, and has not received the SMR Oct-2025 Release 1 security 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 · scopedApply the SMR Oct-2025 Release 1 patch to affected Samsung devices. Until patched, restrict device access to trusted users as the attack requires local proximity.
SMR Oct-2025 Release 1
- 1. Go to Settings on the Samsung Android device
- 2. Navigate to Settings > Software update (or System > Software update depending on Android version)
- 3. Tap 'Download and install' or 'Check for updates'
- 4. If SMR Oct-2025 Release 1 is available, download and install the update
- 5. After installation, verify the patch has been applied by checking Settings > About phone > Software information to confirm the SMR date
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-21050 — 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-21050 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