CVE-2026-21123: Samsung Locksettings improper privilege management

CVE-2026-21123 · Severity: info · Published 2026-10-12

Samsung's Locksettings component, which manages device access controls, contains a privilege management flaw that allows attackers with root access to read data belonging to linked user profiles before the device is unlocked for the first time. This could expose sensitive personal information if a device is compromised at the system level during initial setup.

Technologies: Samsung Android. Vendors: Samsung.

Quick answers

Is CVE-2026-21123 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-21123 being exploited in the wild.
How severe is CVE-2026-21123?
Informational severity, published 12 October 2026.
Which products and versions are affected?
Samsung Android prior to SMR Oct-2026 Release 1.
Is there a fix for CVE-2026-21123?
Yes: fixed in SMR Oct-2026 Release 1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-21123 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-21123?
Check whether you run Samsung Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: SMR Oct-2026 Release 1

Technical details

The vulnerability is an improper privilege management issue in the Locksettings component. It affects Android devices before the October 2026 SMR release and allows local attackers with root privilege to access tied profile data during the pre-unlock state. The attack requires system-level access and occurs in a specific device state (before first unlock).

Affected products

  • Samsung Android prior to SMR Oct-2026 Release 1

Timeline

  • 2026-10-12: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.