CVE-2026-21088 is an improper input validation flaw in libsubextractor.so, triggered while loading a subtitle frame. The record scores it 7.8 (High) and says it lets a local attacker write out-of-bounds memory. Samsung lists the fix in SMR Sep-2026 Release 1.
What's affected
Samsung's September 2026 bulletin lists the libsubextractor.so (subtitle frame loading) issue (SVE-2026-1870) 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-20.
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.
- If your fleet blocks sideloaded apps and limits media apps to your approved list, you reduce the set of local code that could reach this parser. That is a mitigation in spirit only, not a substitute for the patch.
- 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
libsubextractor.so handles subtitle data for media playback. The bug sits in the code that deals with loading a subtitle frame, where input is not validated before it is used to decide how much memory to write. That gives a write outside the intended buffer, a memory safety fault of the kind that can crash a process or, with more work, be turned into code execution.
Media parsers are a recurring source of this class of bug because they process complex, attacker-influenced file formats in native code. The record's local vector means the attacker needs a foothold on the device first.
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 the same bug as the other libsubextractor CVE?
No. Samsung lists two separate entries for this library, one for loading a subtitle frame and one for removing a style tag, each with its own SVE number.
Does the bulletin give a CVSS score?
No. Samsung gives its own severity rating. The 7.8 score comes from the CVE record.
Sources
Last reviewed: 18 October 2026.
