Samsung Devices up to SMR Oct-2026 Release libsimba.heifdec.media.samsung.so input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 2.15- |
Summary
A vulnerability described as very critical has been identified in Samsung Devices. This affects an unknown function of the component libsimba.heifdec.media.samsung.so. The manipulation results in input validation. This vulnerability is known as CVE-2026-21125. Attacking locally is a requirement. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as very critical, was found in Samsung Devices. Affected is an unknown code block of the component libsimba.heifdec.media.samsung.so. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Improper input validation in parsing sheifd in libsimba.heifdec.media.samsung.so prior to SMR Oct-2026 Release 1 allows local attackers to potentially execute arbitrary code.
The advisory is shared for download at security.samsungmobile.com. This vulnerability is traded as CVE-2026-21125 since 12/11/2025. The exploitability is told to be easy. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/12/2026).
Upgrading to version SMR Oct-2026 Release 1 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 1
- 4.1.01.0
- 7
- 8
- 9.0
- 10.0
- 11.0
- 2017-11-03
- 2020-04-02
- 2026
- Go(8.1)
- Go(9.0)
- L
- L(5.1)
- L(5.x)
- M
- M(6.0)
- M(6.x)
- N
- N(7.0)
- N(7.1)
- N(7.x)
- O(8.0)
- O(8.1)
- O(8.X)
- O(8.x)
- Oct-2026
- P(9.0)
- P(9.x)
- Q(10.0)
- Q(10.x)
- R(11.0)
- SMR Aug-2026 Release
- SMR Aug-2026 Release 1
- SMR Feb-2021 Release 1
- SMR Jul-2024 Release
- SMR Jul-2024 Release 1
- SMR Jul-2026 Release
- SMR Mar-2021 Release 1
- SMR Oct-2026 Release
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Devices SMR Oct-2026 Release 1
Timeline
12/11/2025 CVE reserved10/12/2026 Advisory disclosed
10/12/2026 VulDB entry created
10/12/2026 VulDB entry last update
Sources
Vendor: samsung.comAdvisory: security.samsungmobile.com
Status: Confirmed
CVE: CVE-2026-21125 (🔒)
GCVE (CVE): GCVE-0-2026-21125
GCVE (VulDB): GCVE-100-416820
Entry
Created: 10/12/2026 07:31Changes: 10/12/2026 07:31 (66)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.