CVE-2025-21014
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 component in Emergency SoS prior to SMR Aug-2025 Release 1 allows local attackers to access sensitive information.
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 Android component export vulnerability in Samsung's Emergency SoS feature. The application's component(s) are exported without proper access controls, allowing local malicious applications to interact with the component and access sensitive information intended to be protected.
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.
-
Confirm you are using a Samsung Android deviceGo to Settings > About Phone > Device name and manufacturer. Verify the manufacturer is Samsung.Affected if The device is not manufactured by Samsung, the vulnerability does not apply.
-
Check your Android versionGo to Settings > About Phone > Android version. Verify the exact version number displayed.Affected if The version is 13.0, 14.0, or 15.0 exactly - only these specific versions are affected according to the provided advisory.
-
Verify the Emergency SOS feature exists on your deviceGo to Settings > Safety and Emergency (or Settings > Connections > Safety and Emergency) and check if the Emergency SOS option is present and configurable.Affected if The Emergency SOS feature is not present or not accessible, the vulnerability cannot be triggered.
-
Check your current security patch levelGo to Settings > About Phone > Security patch level. Note the date of the last security update.Affected if The security patch level is earlier than August 2025, meaning the SMR Aug-2025 Release 1 patch has not been applied.
You are affected if you have a Samsung Android device running version 13.0, 14.0, or 15.0 with the Emergency SOS feature present and your security patch level is before the August 2025 update.
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 · scopedSamsung has released the SMR Aug-2025 Release 1 patch. Users should update their devices to receive the security patch. Application developers should ensure android:exported="false" is set on sensitive components or implement proper permission checks if export is required.
SMR Aug-2025 Release 1
- Open Settings on your Samsung Android device
- Navigate to Security and Privacy or Software Update
- Check for updates and download the August 2025 Samsung Security Maintenance Release (SMR Aug-2025 Release 1)
- Restart your device after installing the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21014 — 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-21014 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