Local out-of-bounds write via VC1 input validation
Published Aug 10, 2026 · Updated Aug 10, 2026
Improper input validation in VC1 codec of Samsung Mobile Devices before SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. The flaw resides in the VC1 path of libsavsvc.so, but Samsung has not disclosed which input field lacks the bounds check required before a memory write. Reachability requires local access to an Android 14, 15, or 16 device and invocation of the affected codec; the published impact is limited to an out-of-bounds write.
Summary
What happened
Improper input validation in VC1 codec of Samsung Mobile Devices before SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. The flaw resides in the VC1 path of libsavsvc.so, but Samsung has not disclosed which input field lacks the bounds check required before a memory write. Reachability requires local access to an Android 14, 15, or 16 device and invocation of the affected codec; the published impact is limited to an out-of-bounds write.
The record
- CVE
- CVE-2026-21072
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo