CVE-2025-20991
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 Bluetooth prior to SMR Jun-2025 Release 1 allows local attackers to make devices discoverable.
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 · high confidenceImproper export of Android application components in the Bluetooth stack allows any local application to trigger the device to become discoverable. This is an authorization bypass where Bluetooth-related components are accessible without proper access controls, enabling malicious local apps to override user privacy settings.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 Android OS versionGo to Settings > About Phone > Android version (or use 'getprop ro.build.version.release' via ADB)Affected if Version is 13.0, 14.0, or 15.0 on a Samsung device
-
Check Samsung Security Patch LevelGo to Settings > About Phone > Software Information > Security patch level (or use 'getprop ro.build.version.security_patch' via ADB)Affected if Security patch level is earlier than June 2025 SMR (Jun-2025 Release 1)
-
Verify Bluetooth service accessibilityCheck if third-party apps can access Bluetooth visibility controls - attempt to observe if non-system apps can trigger device discoverability without system privilegesAffected if Any local application can make the device discoverable without user consent or system permissions
A Samsung Android device on versions 13.0, 14.0, or 15.0 with a security patch level before June 2025 SMR is likely affected if unauthorized local apps can control Bluetooth discoverability settings.
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 Jun-2025 Release 1 security patch which contains the proper fix. For third-party implementations, ensure Bluetooth components have android:exported="false" or implement appropriate permission checks to restrict access to authorized callers only.
SMR Jun-2025 Release 1 (Samsung Maintenance Release for June 2025)
- 1. Check your Samsung device model and current Android version by going to Settings > About Phone
- 2. Navigate to Settings > Software Update
- 3. Tap 'Download and install' to check for the June 2025 SMR (Samsung Maintenance Release) update
- 4. If the SMR Jun-2025 Release 1 update is available, download and install it
- 5. After installation, verify the device is no longer vulnerable by confirming Bluetooth is not made discoverable by unauthorized local apps
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20991 — 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-20991 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