CVE-2026-49128: Music Player Daemon < 0.24.11 Path Traversal via LocalStorage URI Handling
Music Player Daemon (MPD) before version 0.24.11 contains a path traversal vulnerability in LocalStorage::MapFSOrThrow and LocalStorage::MapUTF8 within the local storage plugin, where the on-disk path is constructed by joining the storage root with a user-supplied URI as plain strings without canonicalization, allowing '..' segments to survive into the resolved path and be flattened by the kernel at openat() time. An unauthenticated attacker can exploit this flaw using the listfiles command to enumerate names, sizes, and modification times of arbitrary directories readable by the MPD process, and the albumart command to read image files in any attacker-chosen directory outside the configured music_directory.
Security readout for executives and security teams
Plain-English summary
MPD versions before 0.24.11 may let an unauthenticated network attacker escape the configured music directory. The attacker could enumerate readable directories and obtain image files accessible to the MPD process. The published impact is confidentiality loss; the supplied evidence does not establish file modification, service disruption, or arbitrary code execution.
Executive priority
Prioritize prompt remediation for internet-facing, broadly reachable, or unauthenticated MPD services. Upgrade those systems first, then reduce service-account permissions and network reachability. Although no active exploitation is established, the high CVSS score, lack of required credentials, and public technical disclosure make delayed remediation an avoidable confidentiality risk.
Technical view
The local storage plugin joins its storage root and a supplied URI without canonicalizing traversal components. Those components can reach filesystem operations and resolve outside the intended root. The affected listfiles behavior exposes directory metadata, while albumart can disclose image files from attacker-selected directories readable by MPD. Version 0.24.11 contains the vendor patch.
Likely exposure
Exposure is most likely where MPD before 0.24.11 is network-reachable and its command interface accepts unauthenticated requests. Consequences depend on the filesystem permissions and accessible directories of the MPD process. Instances isolated from untrusted networks or running with minimal read permissions have reduced, but not eliminated, risk.
Exploitation context
A public technical disclosure describes exploitation of the vulnerable commands, so practical knowledge is available. However, the supplied bundle marks this CVE as absent from KEV and provides no evidence of active exploitation in the wild. Treat it as readily testable rather than confirmed campaign activity.
Researcher notes
CVE-2026-49128 is classified as CWE-22 with CVSS 4.0 score 8.7. The supplied vector indicates network access, low complexity, no privileges, no interaction, and high vulnerable-system confidentiality impact only. Validate both vulnerable mapping functions and the vendor commit when assessing downstream backports; a package version alone may be insufficient if distributors apply patches independently.
Mitigation direction
Upgrade MPD to version 0.24.11 or later using vendor-supported packages.
Restrict MPD command-interface access to trusted hosts until upgrading.
Require authentication where supported and remove unnecessary anonymous access.
Minimize the MPD service account's filesystem read permissions.
Check current vendor guidance for any platform-specific backports or additional precautions.
Validation and detection
Inventory MPD installations and confirm their exact running versions.
Verify all instances run version 0.24.11 or a documented patched backport.
Review network controls governing access to the MPD command interface.
Confirm the MPD account cannot read sensitive directories or unnecessary files.
Review available logs for unusual listfiles or albumart requests containing traversal patterns.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.