In this article
Music Assistant 2.8.0 closes a code execution hole
Music Assistant is an open-source media library manager that connects streaming services to networked speakers. Versions before 2.8.0 let any authenticated user run arbitrary Python code, whatever their role, with the privileges of the server process. NVD rates CVE-2026-73971 at CVSS 3.1 base score 8.0, high.
NVD says a compromise could expose secrets and configuration, alter library data and give control of the application container.
How a return_type argument ends up in eval()
In music_assistant/helpers/api.py, parse_arguments() hands the caller-supplied return_type parameter to parse_value() and Python eval(). This happens for the config/core/get_value, config/providers/get_value and config/players/get_value commands. An attacker can reach those commands through the WebSocket /ws endpoint or the REST JSON-RPC /api endpoint. The code runs before the command handler validates the request, so it executes even when the request later fails.
Every Music Assistant install before 2.8.0 is exposed by default
Check your version: anything before 2.8.0 is affected. A default installation needs no special configuration to be exposed. The CVSS vector marks the attack vector as adjacent, with low privileges required and no user interaction. The NVD record gives no exploitation status and cites no CISA KEV entry.
Update Music Assistant to 2.8.0
Music Assistant 2.8.0 fixes the flaw, so update to it. No workaround is given for users who cannot upgrade to 2.8.0 immediately. NVD references GitHub advisory GHSA-cjp7-8r57-vc8f, the 2.8.0 release tag and pull request 3271 in the Music Assistant server repository.
What NVD has not published on CVE-2026-73971
The NVD record gives no disclosure or patch dates, and its status is Received. It also does not mention Home Assistant, the product the story is tagged with.
| Product | Affected | Fixed |
|---|---|---|
| Music Assistant | before 2.8.0 | 2.8.0 |
Sources
Image: Лапоть, CC0 1.0, via Wikimedia Commons
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].



Discussion