CVE-2026-21100 is an improper access control flaw in SystemUI on Samsung Android devices. The record scores it 7.1 (High) and says a local attacker can launch arbitrary activities. Samsung lists the fix in SMR Sep-2026 Release 1, so install the September 2026 update.
What's affected
Samsung's September 2026 bulletin lists the SystemUI issue (SVE-2026-2314) as affecting Android 14, 15, 16 and 17 on Samsung devices, fixed in SMR Sep-2026 Release 1.
Source conflict to note: the record scores this 7.1 (High), while Samsung's bulletin rates it Moderate. Both are reported here.
Weakness class: CWE-284.
How to check if you're exposed
On a Samsung phone or tablet, open Settings, then About phone, then Software information, and read the Android security patch level. Samsung ships these fixes in the Samsung Mobile Security Maintenance Release (SMR) named in the bulletin, so a September 2026 patch level or later is the thing to look for. If you manage a fleet, your mobile device management console can report the patch level and Android version per device.
The bulletin lists Android 14, 15, 16 and 17 as affected, so any current Samsung device on those versions that has not taken the September 2026 SMR should be treated as exposed. Samsung does not publish a per-model table on the page, so check the update status on the device itself rather than assuming from the model name.
What to do now
- Install the September 2026 Samsung security update (SMR Sep-2026 Release 1) on every managed Samsung device. Carriers sometimes roll it out later than Samsung, so confirm on the device.
- Review which apps on your devices hold overlay or accessibility rights, since those are the usual starting point for abusing UI-level flaws. Remove any you do not need.
- Report the patch level in your MDM inventory and set a compliance rule that flags devices more than one SMR behind.
- Keep the Samsung bulletin as your source of truth, and re-read it, because the vendor updated its vulnerability list after first publication.
Why it matters
SystemUI draws the status bar, notification shade and other parts of the interface, and it runs with elevated rights. Android activities are the screens an app can open, and some of them are meant to be reachable only by the system or by apps with the right permission. If SystemUI will launch an arbitrary activity on behalf of a local caller, it can be used to reach screens the caller should not be able to open.
The record maps this to CWE-284, improper access control, and rates the confidentiality and integrity impact high with no availability impact. It is an authorization mistake rather than a memory fault, so it does not need a crash or exploit chain to work.
The attack vector in the record is local, with low complexity and low privileges required and no user interaction. That means the attacker needs code already running on the device, for example a malicious or compromised app. Local flaws still matter on phones, because the app sandbox is the main wall between one app and the rest of the device, and a bug in a system component can let one app reach beyond it.
The CISA Known Exploited Vulnerabilities flag is false in the record, and the Samsung bulletin we read does not describe exploitation. Treat this as a patch in the normal monthly cycle, not an emergency, but do not let it sit for months.
Quick check
Is this a memory corruption bug?
No. It is an access control flaw, which the record classes as CWE-284.
What does a launched activity let the attacker do?
The sources do not say. The record rates confidentiality and integrity impact as high, so treat it as meaningful.
Sources
Last reviewed: 18 October 2026.
