# CVE-2026-105248: vgmstream TXTP File txtp_parser.c txtp_parse out-of-bounds write

> An out-of-bounds write in vgmstream's TXTP parser allows remote attackers to execute arbitrary code or cause denial of service via crafted files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/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-m8wg-6c2r-mrxp

## What is CVE-2026-105248?

CVE-2026-105248 is a medium-severity memory corruption 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 flaw has been discovered in vgmstream up to r2117. This affects the function parse_params/txtp_parse of the file src/meta/txtp_parser.c of the component TXTP File Handler. The manipulation results in out-of-bounds write. The attack may be launched remotely. The patch is identified as 4669d37a6af94866f6f0628678f9f90d46954e8b. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-105248 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105248 is a medium-severity memory corruption 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-105248 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-105248/ (Markdown: https://insights.sbomify.com/CVE-2026-105248/index.md)
```

## Sources

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

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