CVE-2026-21016: Medium severity Samsung LocationManager vulnerability
Published May 13, 2026
·Updated
Incorrect privilege assignment in LocationManager prior to SMR May-2026 Release 1 allows local attackers to access sensitive information.
Affected Software
83 affected components
Samsung LocationManager<SMR May-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-apr-2026-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-apr-2026-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-apr-2026-r1
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
May 13, 2026
CVE Published
via MITRE·04:56 AM
Data Sourced
via MITRE·04:56 AM
DescriptionWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-21016?
CVE-2026-21016 is categorized as a medium severity vulnerability due to its potential impact on sensitive information access.
2
How do I fix CVE-2026-21016?
To fix CVE-2026-21016, update the Samsung LocationManager to the version released in SMR May-2026 Release 1 or later.
3
Who is affected by CVE-2026-21016?
CVE-2026-21016 affects users of Samsung devices utilizing the LocationManager prior to the SMR May-2026 Release 1.
4
What type of attack is possible with CVE-2026-21016?
CVE-2026-21016 allows local attackers to exploit incorrect privilege assignment to access sensitive information.
5
Is CVE-2026-21016 being actively exploited?
As of the latest updates, there are no reports indicating that CVE-2026-21016 is being actively exploited in the wild.