CVE-2026-26975 json
Music Assistant Server Path Traversal in Playlist Update API Allows Remote Code Execution
published 2026-02-20 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8405
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Music Assistant is an open-source media library manager that integrates streaming services with connected speakers. Versions 2.6.3 and below allow unauthenticated network-adjacent attackers to execute arbitrary code on affected installations. The music/playlists/update API allows users to bypass the .m3u extension enforcement and write files anywhere on the filesystem, which is exacerbated by the container running as root. This can be exploited to achieve Remote Code Execution by writing a malicious .pth file to the Python site-packages directory, which will execute arbitrary commands when Python loads. This issue has been fixed in version 2.7.0.
Patch / fix
- music-assistant music_assistant_server 2.7.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 8 mo ago
Exploit prediction
1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/music-assistant/server/security/advisories/GHSA-7jcc-p6xr-835j referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- music-assistant server
Classification
References
-
github.com
/music-assistant/server/pull/2684
issue-tracking
-
github.com
/music-assistant/server/security/advisories/GHSA-7jcc-p6xr-835j
exploit, vendor-advisory
-
github.com
/music-assistant/server/releases/tag/2.7.0
release-notes
Sources
- CVE List CVE-2026-26975
- NVD CVE-2026-26975
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.