vgmstream up to r2117 txtp src/meta/txtp_parser.c add_entry range_start/range_end resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 2.24 |
Summary
A vulnerability marked as problematic has been reported in vgmstream up to r2117. The affected element is the function add_entry of the file src/meta/txtp_parser.c of the component txtp. Performing a manipulation of the argument range_start/range_end results in resource consumption.
This vulnerability is cataloged as CVE-2026-86515. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in vgmstream up to r2117. It has been classified as problematic. This affects the function add_entry of the file src/meta/txtp_parser.c of the component txtp. The manipulation of the argument range_start/range_end with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-86515. 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 and a public exploit are known. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
Applying the patch 4b6a02dd1aff6428255db912563d77d4cb0a143e is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
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: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 4b6a02dd1aff6428255db912563d77d4cb0a143e
Timeline
09/07/2026 Advisory disclosed09/07/2026 VulDB entry created
09/07/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 1973
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-86515 (🔒)
GCVE (CVE): GCVE-0-2026-86515
GCVE (VulDB): GCVE-100-399669
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/07/2026 21:23Changes: 09/07/2026 21:23 (61)
Complete: 🔍
Submitter: ni-liao
Cache ID: 216::103
Submit
Accepted
- Submit #908370: vgmstream r2117 Resource Consumption (by ni-liao)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.