Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious local app
-
DeliverySupply crafted MKV media file
-
ExploitFramework invokes libsmkvextractor parser
-
ExecutionTrigger out-of-bounds write
-
ImpactExecute arbitrary code in media context
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access to a Samsung mobile device running firmware prior to SMR Oct-2026 Release 1, with the ability to get a crafted MKV/Matroska media file parsed by libsmkvextractor.so (e.g., via a locally-installed app or a media file processed by the device's media framework). The CVSS 4.0 vector shows no privileges (PR:N) and no user interaction (UI:N) are needed, but the local vector (AV:L) means an attacker must already have a foothold on the device or deliver the malicious media to a local processing path - it is not remotely reachable over the network and is limited to Samsung devices below the stated patch level. |
| Impact | This is a moderate-severity local code-execution flaw (vendor CVSS 4.0 base 7.0) in Samsung's libsmkvextractor.so media-extractor library. The provided CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L) indicates a LOCAL attack vector with low complexity, no privileges, and no user interaction required, but impact is driven primarily by high integrity impact (VI:H) with only low confidentiality and availability impact - consistent with an out-of-bounds write that corrupts memory to achieve code execution rather than directly leaking or crashing. No EPSS score, CISA KEV listing, or public POC was provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the AV:L vector further limits mass/remote exploitation. Net: a legitimate patch-priority item for Samsung device fleets given no-privilege/no-interaction local exploitation, but not an emergency relative to remote (AV:N) RCE - realistic abuse requires an attacker to already run code on, or deliver a crafted media file to, the device. No conflicting signals were observed; the main gap is the absence of exploitation-probability (EPSS) and POC telemetry, and a missing CWE (the vendor 'Buffer Overflow' tag and description point to CWE-787 Out-of-bounds Write, not confirmed in input). |
| Exploit ScenarioDerived | A locally-installed malicious or compromised app passes a crafted Matroska/MKV media file to the Samsung media framework, which invokes libsmkvextractor.so to parse it. The malformed container triggers an out-of-bounds write, corrupting memory and allowing the attacker to execute arbitrary code in the context of the media-processing component. No public exploit code was identified at time of analysis, and no user interaction is required per the CVSS vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Out-of-bounds write in Samsung's libsmkvextractor.so media-extraction library allows arbitrary code execution on Samsung mobile devices running firmware prior to SMR Oct-2026 Release 1. Exploitation requires local access - an attacker must already hold a foothold on the device or get a crafted MKV/Matroska media file into a local parsing path - yet the CVSS 4.0 vector requires no privileges and no user interaction (AV:L/PR:N/UI:N), and our independent CVSS 3.1 assessment (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L) rates the impact as high integrity, low confidentiality, and low availability. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV.
RemediationAI
Apply the vendor fix by updating device firmware to SMR Oct-2026 Release 1 or later; Samsung distributes these monthly security releases via OTA and documents them at https://security.samsungmobile.com/securityUpdate.smsb?year=2026&month=10, so the primary action is to confirm the build's SMR level and force an update where devices lag. If the update cannot be deployed immediately, reduce the local attack surface: use MDM or device policy to block installation of untrusted or sideloaded applications that could invoke the media extractor on attacker-controlled input (trade-off: reduced user flexibility and possible enterprise app friction), and restrict or disable untrusted media playback paths so crafted MKV/Matroska files are quarantined rather than fed to the media framework (trade-off: degraded media handling and user inconvenience). Because exploitation requires a local foothold or local delivery of a malicious media file, existing hardening such as Play Protect, app sandboxing, and a locked bootloader meaningfully raises the bar but does not eliminate the flaw, so firmware patching remains the only complete remediation.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
libsmkvextractor.so is a Samsung-proprietary media extractor library that parses and demuxes MKV/Matroska container files within Samsung mobile firmware. The defect is a memory-safety flaw - an out-of-bounds write of the CWE-787 class, although no CWE identifier was assigned in the source data - triggered when malformed MKV structures are parsed, allowing attacker-controlled data to overwrite memory adjacent to the intended buffer and corrupt execution flow toward code execution. Reachability is local (AV:L): the library is invoked through the on-device media framework, either by a locally installed application or when a media file is processed on the device, so the flaw is not remotely reachable over the network. The CVSS 4.0 vector records PR:N and UI:N, and our independent CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L) is consistent - low confidentiality, high integrity, and low availability impact with no scope change - meaning the primary consequence is integrity compromise through arbitrary code execution in the context of the media-extraction process, limited to Samsung devices below the stated patch level.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
Local media-file parsing path (AV:L) reachable by an unprivileged local app with no interaction (PR:N/UI:N); out-of-bounds write yields code execution so I:H, with limited C and A impact.
Primary rating from Vendor (samsung).
CVSS VectorVendor: samsung
DescriptionCVE.org
Out-of-bounds write in libsmkvextractor.so prior to SMR Oct-2026 Release 1 allows local attackers to execute arbitrary code.
Articles & Coverage 2
Executive ViewAI
Samsung mobile devices running firmware older than the SMR Oct-2026 Release 1 carry an out-of-bounds write in the libsmkvextractor.so media-extraction library that can be turned into arbitrary code execution on the handset. Because the vulnerable component parses MKV/Matroska media, every employee carrying an unpatched Samsung device in a BYOD or corporate-managed fleet represents a potential foothold into corporate mail, VPN sessions, and MFA token stores. Leadership should treat this as a fleet-wide mobile hygiene and inventory problem rather than a niche media-parsing defect, since the exposed population is large, hard to enumerate, and currently has no vendor patch.
No vendor-released patch identified at time of analysis. Interim mitigations: apply SMR Oct-2026 Release 1 or later firmware where available; block or strip MKV/Matroska media at the email gateway and MDM content filter; disable unknown-source sideloading and restrict third-party media players; require fully updated managed devices for corporate email, VPN, and MFA access; and monitor Samsung endpoints for anomalous code execution originating from the media-extraction process.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-97178
GHSA-xjm9-873m-p5vv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB