# CVE-2026-49127: Music Player Daemon < 0.24.11 Stack Buffer Overflow via pcm_unpack_24be

> Unauthenticated attackers can trigger a stack buffer overflow in MPD via malicious HTTP audio sources, potentially leading to code execution or service termination.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-49127, GHSA-p9r5-qpp4-rjg3, UBUNTU-CVE-2026-49127

## What is CVE-2026-49127?

CVE-2026-49127 is a high-severity memory corruption vulnerability in MusicPlayerDaemon MPD, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Music Player Daemon (MPD) before version 0.24.11 contains a stack buffer overflow vulnerability in the pcm_unpack_24be function in src/pcm/Pack.cxx that allows unauthenticated attackers to corrupt stack memory by triggering an off-by-one write in the PCM decoder plugin. Attackers can issue two MPD commands referencing a malicious HTTP audio source to cause the unpack loop to write 1366 entries into a 1365-entry buffer, overwriting four bytes past the array boundary with three attacker-controlled bytes from an HTTP response body, resulting in daemon termination or potential code execution.

Weakness: CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2026-49127?


## How do I fix CVE-2026-49127?

Upgrade to a fixed version.

## Is CVE-2026-49127 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49127 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49127 and fix it if it is affected.

What it is: CVE-2026-49127 is a high-severity memory corruption vulnerability in MusicPlayerDaemon MPD, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49127 exists.

Affected product: MusicPlayerDaemon MPD. 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-2026-49127/ (Markdown: https://insights.sbomify.com/CVE-2026-49127/index.md)
```

## Sources

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

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