Samsung HEIF Decoder EUVD-2026-97188

Exploitation requires the vulnerable cover-image parsing path in libsimba.heifdec.media.samsung.so to process attacker-controlled HEIF input on the device - i.e., a crafted HEIF file (or its embedded cover image) must be opened/decoded locally, typically via a malicious app or a file an attacker can get processed. Limiting factors: the attack vector is local (AV:L), so no remote/network reachability exists and the attacker needs on-device execution or the ability to place and have a malicious file parsed; the issue is fixed in SMR Oct-2026 Release 1, so patched devices are not affected. Per the CVSS 4.0 vector no privileges (PR:N) and no user interaction (UI:N) are required beyond the crafted input reaching the decoder.

The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H, score 8.6) indicates a local attack vector with low complexity, no privileges, and no user interaction, yielding high confidentiality, integrity, and availability impact - consistent with memory-corruption-style arbitrary code execution in a media decoder. Critically, this is a LOCAL vulnerability (AV:L), not remotely reachable over the network, which materially lowers real-world exploitability versus the high base score: an attacker needs an execution foothold or the ability to get a crafted HEIF cover image processed on the device. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: a genuinely serious code-execution flaw in a Samsung media library warranting prompt patching via the Oct-2026 SMR, but the local-only vector plus absence of KEV/EPSS/POC signals suggests it is not a drop-everything internet-facing emergency; prioritize based on Samsung device fleet exposure rather than mass-exploitation risk.

A malicious or compromised app on a Samsung device, or a crafted HEIF file delivered to the device and processed locally, triggers the cover-image parsing path in libsimba.heifdec. Improper input validation leads to memory corruption that the attacker leverages to execute arbitrary code in the context of the decoding process. No public exploit code is identified at time of analysis, and because the vector is local (AV:L) the attacker must already be able to run code or place a file on the device.