# CVE-2025-9809: Memory corruption in libretro-common

> Remote attackers can execute arbitrary code via a crafted .cue file causing an out-of-bounds write in the libretro-common library.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-9809, GHSA-2cg7-x3pg-q7xf, UBUNTU-CVE-2025-9809, USN-8166-1

## What is CVE-2025-9809?

CVE-2025-9809 is a high-severity memory corruption vulnerability in libretro-common, published on 1 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Out-of-bounds write in cdfs_open_cue_track in libretro libretro-common latest on all platforms allows remote attackers to execute arbitrary code via a crafted .cue file with a file path exceeding PATH_MAX_LENGTH that is copied using memcpy into a fixed-size buffer.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-9809?

It affects 1 product.


Products: Libretro Libretro-Common.

## How do I fix CVE-2025-9809?

Apply the vendor's patch.

## Is CVE-2025-9809 being exploited?

There is no known exploitation of CVE-2025-9809 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9809 and fix it if it is affected.

What it is: CVE-2025-9809 is a high-severity memory corruption vulnerability in libretro-common, published on 1 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-9809 in the wild and no public exploit code.

Affected product: libretro-common. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9809/ (Markdown: https://insights.sbomify.com/CVE-2025-9809/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9809
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9809
- OSV: https://osv.dev/vulnerability/CVE-2025-9809

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9809/
Summaries are generated and may contain mistakes; the official description above is the record.