vgmstream up to r2117 Microsoft IMA Decoder src/coding/ima_decoder.c decode_ms_ima divide by zero
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.26 |
Summary
A vulnerability identified as problematic has been detected in vgmstream up to r2117. Affected by this vulnerability is the function decode_ms_ima of the file src/coding/ima_decoder.c of the component Microsoft IMA Decoder. Performing a manipulation results in divide by zero.
This vulnerability is reported as CVE-2026-105250. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in vgmstream up to r2117. It has been classified as problematic. This affects the function decode_ms_ima of the file src/coding/ima_decoder.c of the component Microsoft IMA Decoder. The manipulation with an unknown input leads to a divide by zero vulnerability. CWE is classifying the issue as CWE-369. The product divides a value by zero. This is going to have an impact on availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-105250. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-92277). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
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: Divide by zeroCWE: CWE-369 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/04/2026 Advisory disclosed10/04/2026 VulDB entry created
10/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 1999
Status: Confirmed
CVE: CVE-2026-105250 (🔒)
GCVE (CVE): GCVE-0-2026-105250
GCVE (VulDB): GCVE-100-413457
EUVD: 🔒
Entry
Created: 10/04/2026 19:42Updated: 10/05/2026 11:47
Changes: 10/04/2026 19:42 (53), 10/05/2026 11:47 (1)
Complete: 🔍
Submitter: ni-liao
Cache ID: 216::103
Submit
Accepted
- Submit #976280: vgmstream r2117 Divide by Zero (by ni-liao)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.