high CVSS 8.8

CVE-2026-26975·Python vulnerability

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.

Severity
high
Software
Python
Fixed in
2.7.0
Published
2026-02-20

Affected versions

Until: 2.7.0

Fixed in: 2.7.0

How to fix this CVE

Update Music Assistant to version 2.7.0 or later to remediate the arbitrary file write vulnerability in the playlist API. This patch enforces strict file extension validation and prevents unauthorized filesystem access that could lead to code execution. If you are running Music Assistant in a containerized environment, rebuild your images with the patched version and redeploy immediately.

sudo dnf check-update python3-musicassistant && sudo dnf update python3-musicassistant

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /music/playlists/update.*Content-Disposition.*filename=.*\.pth|POST /music/playlists/update.*site-packages|POST /music/playlists/update.*\.\.\/(lib|usr|etc)

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Implement a WAF rule to block all POST requests to /music/playlists/update that contain file extensions other than .m3u in the filename parameter or Content-Disposition header; additionally reject requests containing path traversal sequences (../) or references to Python directories (site-packages, dist-packages).

How to check if you are affected

  1. Run 'python3 -m pip show musicassistant' or check the application UI to retrieve the installed version number; confirm it is below 2.7.0
  2. Verify if the music/playlists/update API endpoint is exposed on the network by testing curl -X POST http://<target>:8181/music/playlists/update (default port may vary)
  3. Search application and system logs for POST requests to /music/playlists/update with file paths containing '.pth' extensions or references to site-packages directories
  4. After patching, re-run 'python3 -m pip show musicassistant' and confirm the version is 2.7.0 or higher; verify API file upload requests are now rejected for non-.m3u files

FAQ

What is CVE-2026-26975?

CVE-2026-26975 is a critical vulnerability in Music Assistant that allows unauthenticated attackers on the same network to upload arbitrary files and execute malicious Python code by exploiting insufficient input validation in the playlist update API.

Is CVE-2026-26975 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available, though the attack is relatively straightforward to execute.

What versions of Music Assistant are affected by CVE-2026-26975?

All versions of Music Assistant up to and including 2.6.3 are vulnerable; version 2.7.0 and later contain the fix.

How do I check if my server is vulnerable to CVE-2026-26975?

Execute 'python3 -m pip show musicassistant' to check the installed version; if it reports a version ≤ 2.6.3, your installation is vulnerable.

Does Defensia detect CVE-2026-26975?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Music Assistant or Python is installed on a monitored server, CVE-2026-26975 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-25115CVSS 9.9n8n is an open source workflow automation platform. Prior to version 2.4.8, a vulnerability in the Python Code node allows authenticated users to break out of the Python sandbox environment and execute code outside the intended security boundary. This issue has been patched in version 2.4.8.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-26975. Free for 1 server.

Get started free