# CVE-2026-105250: vgmstream Microsoft IMA Decoder ima_decoder.c decode_ms_ima divide by zero

> A remote attacker can cause a denial of service in vgmstream by triggering a divide by zero error in the Microsoft IMA decoder.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-3mmp-rh6q-jfhh

## What is CVE-2026-105250?

CVE-2026-105250 is a medium-severity denial of service vulnerability in vgmstream, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A security vulnerability has been detected in vgmstream up to r2117. Affected is the function decode_ms_ima of the file src/coding/ima_decoder.c of the component Microsoft IMA Decoder. Such manipulation leads to divide by zero. The attack can be executed remotely.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2026-105250?


## How do I fix CVE-2026-105250?

No fix has been published for CVE-2026-105250 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105250 being exploited?

There is no known exploitation of CVE-2026-105250 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105250 and fix it if it is affected.

What it is: CVE-2026-105250 is a medium-severity denial of service vulnerability in vgmstream, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-105250 in the wild and no public exploit code.

Affected product: vgmstream. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105250/ (Markdown: https://insights.sbomify.com/CVE-2026-105250/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105250
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105250
- OSV: https://osv.dev/vulnerability/CVE-2026-105250

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105250/
Summaries are generated and may contain mistakes; the official description above is the record.