Code execution via oversized CUE file path
Published Sep 1, 2025 · Updated Sep 1, 2025
Out-of-bounds write in Libretro libretro-common allows remote attackers to execute arbitrary code through a crafted .cue file. Within cdfs_open_cue_track, memcpy uses the untrusted file-path length as its copy size even when that length exceeds the fixed PATH_MAX_LENGTH destination buffer. Exploitation requires a vulnerable consumer to process the attacker-supplied CUE file; the CNA assessment treats delivery as local and requires active user interaction.
Summary
What happened
Out-of-bounds write in Libretro libretro-common allows remote attackers to execute arbitrary code through a crafted .cue file. Within cdfs_open_cue_track, memcpy uses the untrusted file-path length as its copy size even when that length exceeds the fixed PATH_MAX_LENGTH destination buffer. Exploitation requires a vulnerable consumer to process the attacker-supplied CUE file; the CNA assessment treats delivery as local and requires active user interaction.
The record
- CVE
- CVE-2025-9809
- Published
- Sep 1, 2025
- Updated
- Sep 1, 2025
- Vendor
- Libretro
- Product
- libretro-common
- Classifications
- CWE-787, CAPEC-100, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2025CVE publishedPublication date reported by the CVE source.
- Sep 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted CUE file example in upstream issue 222proof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo