CVE-2026-116726 json
gbsplay through 0.0.103 Heap Out-of-Bounds Read via gbr_open GBR Title
published 2026-10-26 13 d ago modified 2026-10-27 12 d ago also EUVD-2026-110474
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
Gbsplay through 0.0.103 contains a heap out-of-bounds read vulnerability in gbr_open() in gbs.c that fails to verify file length before scanning the GBR ROM title field. Attackers can supply a crafted GBR file of 0x21 to 0x162 bytes to read past the heap buffer, crashing gbsplay or leaking memory.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12 d ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- mmitch gbsplay
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/mmitch/gbsplay/commit/33812ed38d84b800b5a17f639ef6625f76290785
patch
-
github.com
/mmitch/gbsplay/issues/201
issue-tracking
-
github.com
/mmitch/gbsplay
product
-
github.com
/mmitch/gbsplay/blob/0.0.103/gbs.c#L810-L820
technical-description
-
hackmd.io
/@haindpwn/gbsplay-rom-bank-index-oob-read
third-party-advisory
-
vulncheck.com
/advisories/gbsplay-through-0.0.103-heap-out-of-bounds-read-via-gbr-open-gbr-title
third-party-advisory
Sources
- CVE List CVE-2026-116726
- NVD CVE-2026-116726
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.