CVE-2026-21069: Samsung Mobile Devices · Incorrect Conversion Between Numeric Types
Affects Samsung Mobile DevicesSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Samsung MobileSamsung Mobile Devices | Affected– | Fixed in– |
AI-suggested
Until an official fix is released, users should apply the SMR August 2026 Release 1 once available, as it is implied to address this issue. No additional vendor-provided mitigation instructions are currently available.
Description
CVE-2026-21069 is a medium severity vulnerability in Samsung Mobile Devices involving an incorrect conversion between numeric types in the VC1 codec component (libsavsvc.so). This flaw allows local attackers to write out-of-bounds memory, potentially leading to memory corruption. The issue affects versions prior to the Samsung Mobile SMR August 2026 Release 1. No official patch or remediation guidance has been provided yet, and there are no known exploits in the wild.