vgmstream AWB parser src/meta/awb.c init_vgmstream_awb_memory divide by zero
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 2.30 |
Summary
A vulnerability marked as problematic has been reported in vgmstream. The impacted element is the function init_vgmstream_awb_memory of the file src/meta/awb.c of the component AWB parser. Performing a manipulation results in divide by zero.
This vulnerability is reported as CVE-2026-92881. The attack is possible to be carried out remotely. No exploit exists.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in vgmstream (the affected version is unknown). It has been classified as problematic. This affects the function init_vgmstream_awb_memory of the file src/meta/awb.c of the component AWB parser. 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.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-92881. 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 of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Applying the patch ae37662ad626254ddd96ad69ac263792d7a92024 is able to eliminate this problem. The bugfix is ready for download at github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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
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: ae37662ad626254ddd96ad69ac263792d7a92024
Timeline
09/17/2026 Advisory disclosed09/17/2026 VulDB entry created
09/17/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 1996
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-92881 (🔒)
GCVE (CVE): GCVE-0-2026-92881
GCVE (VulDB): GCVE-100-406347
Entry
Created: 09/17/2026 10:23Changes: 09/17/2026 10:23 (56)
Complete: 🔍
Submitter: ni-liao
Cache ID: 216::103
Submit
Accepted
- Submit #942165: vgmstream r2117 Divide by Zero (by ni-liao)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.