CVE-2025-21080
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 export of android application components in Dynamic Lockscreen prior to SMR Dec-2025 Release 1 allows local attackers to access files with Dynamic Lockscreen's privilege.
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 Android component export vulnerability in Samsung's Dynamic Lockscreen app. The app improperly exports certain components (activities, services, or broadcast receivers) that can be invoked by other local applications, allowing a malicious local app to access files with Dynamic Lockscreen's elevated privileges.
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= 15.0= 16.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
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Find the Samsung Dynamic Lockscreen app packageRun 'pm list packages | grep -i dynamiclock' or 'pm list packages | grep -i dlock' to locate the package nameAffected if No package found means the app is not installed and the device is not affected
-
Check the installed version of Dynamic LockscreenRun 'dumpsys package <package_name>' and look for 'versionName' under the package info, or use 'pm dump <package_name>'Affected if Version is exactly 15.0 or 16.0 - these are the affected versions
-
Verify exported components in the app manifestRun 'pm dump <package_name> | grep -A 5 "android:exported"' to see if activities, services, or receivers have android:exported=trueAffected if Any activity, service, or receiver component shows android:exported=true, meaning other apps can invoke it
-
Confirm the vulnerability requires the Dynamic Lockscreen feature to be activeCheck if the app is set as the active lockscreen or if Dynamic Lockscreen widgets are enabled in device settingsAffected if The app is installed with affected version AND components are exported AND the user uses Dynamic Lockscreen as their lockscreen or has added Dynamic Lockscreen widgets
The device is affected only if Samsung Dynamic Lockscreen app version 15.0 or 16.0 is installed AND has exported components that can be invoked by other local applications, allowing privilege escalation.
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 Samsung SMR Dec-2025 Release 1 or later OTA update to affected devices to patch the improperly exported components.
SMR Dec-2025 Release 1 or later
- Check for system updates on your Samsung Android device
- Navigate to Settings > Security and privacy > Security update or Settings > Software update
- Ensure the device is updated to the December 2025 Samsung Security Maintenance Release (SMR) or later
- Verify the security patch level is December 2025 or higher after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,672.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21080 — 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-21080 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