CVE-2026-21090 is an out-of-bounds write in libsaviextractor.so on Samsung Android devices. The record scores it 7.8 (High) and says a local attacker can write out-of-bounds memory. 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 libsaviextractor.so issue (SVE-2026-1989) 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.8 (High), while Samsung's bulletin rates it Moderate. Both are reported here.
Weakness class: CWE-787.
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.
- Check that your approved app list does not include players or editors you cannot account for. Fewer apps that parse media means fewer ways to reach the library.
- 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
libsaviextractor.so is a media extraction library. An out-of-bounds write (CWE-787) in native code corrupts memory outside the buffer the code meant to use. The advisories do not describe the exact trigger, and we will not guess at one. What matters for defenders is the class: memory corruption in a library that processes media, reachable from a local app.
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 there a workaround?
The bulletin we read lists none. The remedy is the SMR Sep-2026 Release 1 update.
How much detail does Samsung give?
Very little. The entry names the library and the weakness type only, which is typical for Samsung bulletins.
Sources
Last reviewed: 18 October 2026.
