CVE-2026-21011
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 · uneditedIncorrect privilege assignment in Bluetooth in Maintenance mode prior to SMR Apr-2026 Release 1 allows physical attackers to bypass Extend Unlock.
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 vulnerability exists in Bluetooth functionality when the device is in Maintenance mode. An incorrect privilege assignment allows a physical attacker to bypass the Extend Unlock security feature, which normally extends the unlock state of the device. The issue affects devices running versions prior to the SMR Apr-2026 Release 1.
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= 14.0= 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 versionGo to Settings > About Phone > Android version and verify the installed version is 14.0, 15.0, or 16.0Affected if Android version matches 14.0, 15.0, or 16.0 and the SMR version is prior to Apr-2026 Release 1
-
Confirm device is SamsungVerify the device manufacturer is Samsung in Settings > About Phone > Manufacturer or ModelAffected if Device is a Samsung Android device running the affected versions
-
Check SMR versionGo to Settings > About Phone > Software information > Build number or SMR (Samsung Maintenance Release) version field to identify the specific SMR buildAffected if SMR version is before the Apr-2026 Release 1 patch
-
Verify Maintenance mode statusCheck if Bluetooth Maintenance mode is enabled on the device - this is typically found in Settings > Developer options > Bluetooth Maintenance mode or Settings > Connections > Bluetooth > Maintenance modeAffected if Bluetooth Maintenance mode is currently enabled or has been used on the device
-
Check Extend Unlock configurationVerify the Extend Unlock security feature status in Settings > Lock screen > Extend Unlock or Settings > Security > Extend Unlock settingsAffected if Extend Unlock feature is configured and the device is vulnerable to bypass via Maintenance mode
User is affected if running Samsung Android 14.0, 15.0, or 16.0 with an SMR version prior to Apr-2026 Release 1 and the device has Bluetooth Maintenance mode capability available.
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 · scopedUpdate to SMR Apr-2026 Release 1 or later to receive the patch for this privilege assignment issue in Bluetooth Maintenance mode.
SMR Apr-2026 Release 1 or later
- Navigate to Settings > Software Update on the Samsung device
- Check for and download the SMR Apr-2026 Release 1 update or later
- Install the system update to receive the Bluetooth security patch
- After updating, verify the patch is applied by checking Settings > About Phone > Software Information > Samsung Security version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21011 — 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-2026-21011 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