CVE-2026-105248

Deferred Deferred - Pending Action

BaseFortify

Publication date: 2026-10-05

Last updated on: 2026-10-06

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-05

Last Modified

2026-10-06

Generated

2026-10-19

AI Q&A

2026-10-05

EPSS Evaluated

2026-10-18

NVD

CVE-2026-105248

EUVD

EUVD-2026-92274

Affected Vendors & Products

Vendor	Product	Version / Range
n/a	vgmstream	r2117

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-119	The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

This vulnerability is an out-of-bounds write flaw in vgmstream up to r2117, specifically in the TXTP file handler function parse_params/txtp_parse within src/meta/txtp_parser.c. It occurs when processing crafted TXTP files, leading to memory corruption due to improper handling of attacker-controlled parameters like 'from' and 'count' in the sbuf_silence_part() function. The issue allows remote attackers to manipulate memory, potentially crashing the application or enabling further exploits.

Detection Guidance

Detecting this vulnerability requires checking for vulnerable versions of vgmstream and analyzing TXTP files for malformed input. Inspect the version of vgmstream in use with commands like 'vgmstream-cli --version' or 'find / -name vgmstream-cli 2>/dev/null'. Review TXTP files for unusual parameters or negative values in silence padding fields. Monitor for crashes or memory corruption during audio file processing.

Impact Analysis

This vulnerability can impact you by causing crashes or instability in applications using vulnerable versions of vgmstream. If exploited, it may allow attackers to corrupt memory, leading to arbitrary code execution or denial-of-service conditions. The impact depends on how vgmstream is embedded in your environment, such as media players or audio processing tools.

Compliance Impact

The vulnerability involves an out-of-bounds write in vgmstream's TXTP file handler, which could lead to memory corruption, crashes, or potential arbitrary code execution. This type of vulnerability may compromise data integrity and confidentiality, which are critical for compliance with standards like GDPR and HIPAA. GDPR requires protecting personal data integrity and confidentiality, while HIPAA mandates safeguarding protected health information. Exploitation of this flaw could result in unauthorized access or data breaches, violating these compliance requirements.

Mitigation Strategies

Apply the patch commit 4669d37a6af94866f6f0628678f9f90d46954e8b to vgmstream. Update to the latest version if available. Restrict access to TXTP file processing functions. Validate all TXTP file inputs to reject negative or out-of-bounds parameters. Monitor for crashes or memory corruption in processes handling audio files.

Hi! I’m here to help you understand CVE-2026-105248. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70