Daemon crash via PCM decoder off-by-one write
Published May 28, 2026 · Updated May 28, 2026
Stack buffer overflow in Music Player Daemon before 0.24.11 allows remote attackers to crash the daemon through malicious L24 audio. pcm_unpack_24be processes a full 4,096-byte FIFO as 1,366 samples but receives storage for 1,365, causing a four-byte stack write. An attacker needs MPD protocol access and an attacker-controlled HTTP audio source; unhardened builds also incur adjacent stack corruption.
Summary
What happened
Stack buffer overflow in Music Player Daemon before 0.24.11 allows remote attackers to crash the daemon through malicious L24 audio. pcm_unpack_24be processes a full 4,096-byte FIFO as 1,366 samples but receives storage for 1,365, causing a four-byte stack write. An attacker needs MPD protocol access and an attacker-controlled HTTP audio source; unhardened builds also incur adjacent stack corruption.
The record
- CVE
- CVE-2026-49127
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Music Player Daemon
- Product
- Music Player Daemon
- Classifications
- CWE-193, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record 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 <0.24.11
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- MPD pcm_unpack_24be L24 reproductionproof of concept · demonstrated
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