Game Music Emu (libgme) through 0.6.5 contains a heap out-of-bounds read vulnerability in the AY loader get_data function caused by an integer underflow in the track-table bounds check. Attackers can supply a crafted ZXAYEMUL file with an oversized track table to read past the file buffer via gme_track_info or gme_start_track, crashing libgme consumers.
CVE-2026-111152
MEDIUMPre-NVD 5.55.5Trending — 4 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.5 from GitHub Security Advisory published 2026-10-15. A secondary CVSS source baseline 5.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
5.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 5.5
- EG Score
- 5.5MEDIUMhigh confidence
- EG Risk
- 41EG Risk 41/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity55% × 45%The EG Score, 5.5 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.1%
- EPSS %ILE
- 2nd
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 15, 2026
Last Modified
October 16, 2026
Advisory Details (5)
Auto-updated Oct 15, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page
Game Music Emu (libgme) through 0.6.5 Heap Out-of-Bounds Read via AY Loader | Advisories | VulnCheck
https://www.vulncheck.com/advisories/game-music-emu-libgme-through-0.6.5-heap-out-of-bounds-read-via-ay-loaderWeb page
libgme (Game Music Emu) 0.6.5: out-of-bounds read in the AY loader through an integer underflow in the get_data track-table bounds check - HackMD
https://hackmd.io/@haind-pwn/libgme-ay-track-table-underflow-oob-readGitHub commit
commit ae10a8f05479 (libgme/game-music-emu)
Fix landed in libgme/game-music-emu commit ae10a8f05479 — awaiting tagged release
https://github.com/libgme/game-music-emu/commit/ae10a8f05479e3c8f80429e7a59759fed06f8c13Web page
game-music-emu/gme/Ay_Emu.cpp at 9e23d10f9fd2a6a2f33b10912dd8dc7153258995 · libgme/game-music-emu · GitHub
https://github.com/libgme/game-music-emu/blob/9e23d10f9fd2a6a2f33b10912dd8dc7153258995/gme/Ay_Emu.cpp#L53-L80Web page
GitHub - libgme/game-music-emu: Blargg's video game music emulation library, which allows audio applications to easily add playback support for the music of many classic video game consoles. · GitHub
https://github.com/libgme/game-music-emuVendor Advisories for CVE-2026-111152(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-16 18:32 UTCEG score recompute
- 2026-10-16 18:32 UTCGHSA enrichmentGHSA-wm76-g833-ghjv · GitHub CVSS 5.5
- 2026-10-16 17:31 UTCEG score recompute
- 2026-10-16 17:31 UTCGHSA enrichmentGHSA-wm76-g833-ghjv · GitHub CVSS 5.5
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-15 19:38 UTCEG score recompute
- 2026-10-15 19:04 UTCEG score recomputeFirst assessed: 5.5 MEDIUM
- 2026-10-15 19:02 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-111152?
CVE-2026-111152 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. Game Music Emu (libgme) through 0.6.5 contains a heap out-of-bounds read vulnerability in the AY loader getdata function caused by an integer underflow in the track-table bounds check. Attackers can supply a crafted ZXAYEMUL file with an oversized track table to read past the file buffer via…
When was CVE-2026-111152 made public?
CVE-2026-111152 was made public on October 15, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-111152 actively exploited?
CVE-2026-111152 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111152?
CVE-2026-111152 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111152?
An upstream fix for CVE-2026-111152 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-111152 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-111152
Is Your Infrastructure Affected by CVE-2026-111152?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.