CVE-2026-21011: Medium severity Samsung Samsung SMR vulnerability
Published Apr 13, 2026
·Updated
Incorrect privilege assignment in Bluetooth in Maintenance mode prior to SMR Apr-2026 Release 1 allows physical attackers to bypass Extend Unlock.
Affected Software
80 affected components
Samsung Samsung SMR<SMR Apr-2026 Release 1
Samsung Android=14.0
Samsung Android=14.0-smr-apr-2022-r1
Samsung Android=14.0-smr-apr-2023-r1
Samsung Android=14.0-smr-apr-2024-r1
Samsung Android=14.0-smr-apr-2025-r1
Samsung Android=14.0-smr-aug-2022-r1
Samsung Android=14.0-smr-aug-2023-r1
Samsung Android=14.0-smr-aug-2024-r1
Samsung Android=14.0-smr-aug-2025-r1
Samsung Android=14.0-smr-dec-2021-r1
Samsung Android=14.0-smr-dec-2022-r1
Samsung Android=14.0-smr-dec-2023-r1
Samsung Android=14.0-smr-dec-2024-r1
Samsung Android=14.0-smr-dec-2025-r1
Samsung Android=14.0-smr-feb-2022-r1
Samsung Android=14.0-smr-feb-2023-r1
Samsung Android=14.0-smr-feb-2024-r1
Samsung Android=14.0-smr-feb-2025-r1
Samsung Android=14.0-smr-feb-2026-r1
Samsung Android=14.0-smr-jan-2022-r1
Samsung Android=14.0-smr-jan-2023-r1
Samsung Android=14.0-smr-jan-2024-r1
Samsung Android=14.0-smr-jan-2025-r1
Samsung Android=14.0-smr-jan-2026-r1
Samsung Android=14.0-smr-jul-2022-r1
Samsung Android=14.0-smr-jul-2023-r1
Samsung Android=14.0-smr-jul-2024-r1
Samsung Android=14.0-smr-jul-2025-r1
Samsung Android=14.0-smr-jun-2022-r1
Samsung Android=14.0-smr-jun-2023-r1
Samsung Android=14.0-smr-jun-2024-r1
Samsung Android=14.0-smr-jun-2025-r1
Samsung Android=14.0-smr-mar-2022-r1
Samsung Android=14.0-smr-mar-2023-r1
Samsung Android=14.0-smr-mar-2024-r1
Samsung Android=14.0-smr-mar-2025-r1
Samsung Android=14.0-smr-mar-2026-r1
Samsung Android=14.0-smr-may-2022-r1
Samsung Android=14.0-smr-may-2023-r1
Samsung Android=14.0-smr-may-2024-r1
Samsung Android=14.0-smr-may-2025-r1
Samsung Android=14.0-smr-nov-2021-r1
Samsung Android=14.0-smr-nov-2022-r1
Samsung Android=14.0-smr-nov-2023-r1
Samsung Android=14.0-smr-nov-2024-r1
Samsung Android=14.0-smr-nov-2025-r1
Samsung Android=14.0-smr-oct-2022-r1
Samsung Android=14.0-smr-oct-2023-r1
Samsung Android=14.0-smr-oct-2024-r1
Samsung Android=14.0-smr-oct-2025-r1
Samsung Android=14.0-smr-sep-2022-r1
Samsung Android=14.0-smr-sep-2023-r1
Samsung Android=14.0-smr-sep-2024-r1
Samsung Android=14.0-smr-sep-2025-r1
Samsung Android=15.0
Samsung Android=15.0-smr-apr-2025-r1
Samsung Android=15.0-smr-aug-2025-r1
Samsung Android=15.0-smr-dec-2025-r1
Samsung Android=15.0-smr-feb-2025-r1
Samsung Android=15.0-smr-feb-2026-r1
Samsung Android=15.0-smr-jan-2025-r1
Samsung Android=15.0-smr-jan-2026-r1
Samsung Android=15.0-smr-jul-2025-r1
Samsung Android=15.0-smr-jun-2025-r1
Samsung Android=15.0-smr-mar-2025-r1
Samsung Android=15.0-smr-mar-2026-r1
Samsung Android=15.0-smr-may-2025-r1
Samsung Android=15.0-smr-nov-2025-r1
Samsung Android=15.0-smr-oct-2025-r1
Samsung Android=15.0-smr-sep-2025-r1
Samsung Android=16.0
Samsung Android=16.0-smr-aug-2025-r1
Samsung Android=16.0-smr-dec-2025-r1
Samsung Android=16.0-smr-feb-2026-r1
Samsung Android=16.0-smr-jan-2026-r1
Samsung Android=16.0-smr-mar-2026-r1
Samsung Android=16.0-smr-nov-2025-r1
Samsung Android=16.0-smr-oct-2025-r1
Samsung Android=16.0-smr-sep-2025-r1
Event History
Apr 13, 2026
CVE Published
via MITRE·05:04 AM
Data Sourced
via MITRE·05:04 AM
DescriptionWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-21011?
CVE-2026-21011 is considered to have high severity due to the risk of physical attackers bypassing security measures.
2
How do I fix CVE-2026-21011?
To fix CVE-2026-21011, you should update your device to the latest Samsung SMR version, specifically the SMR Apr-2026 Release 1.
3
What systems are impacted by CVE-2026-21011?
CVE-2026-21011 affects Samsung devices running Android version 14.0 and earlier SMR updates.
4
What are the risks associated with CVE-2026-21011?
The main risk of CVE-2026-21011 is that it allows physical attackers to bypass the device unlock feature in maintenance mode.
5
Is there a temporary workaround for CVE-2026-21011?
Currently, the recommended response is to update the device as there are no documented temporary workarounds for CVE-2026-21011.