Music Assistant server versions below 2.7.0 are susceptible to unauthenticated remote code execution, posing a critical risk to host system integrity.

The application fails to properly enforce file extension restrictions within the music/playlists/update API, allowing unauthenticated, network-adjacent attackers to perform path traversal and write arbitrary files. By placing a malicious .pth file into the Python site-packages directory, an attacker can achieve remote code execution, particularly since the application often runs with root privileges.

Successful exploitation allows an unauthenticated attacker to gain full control over the host server, leading to complete compromise of the media library and underlying infrastructure. Given the CVSS score of 8.8, this vulnerability represents a high-severity risk that could result in unauthorized data access, system disruption, and potential lateral movement within the network.

Immediate Action: Upgrade the Music Assistant server to version 2.7.0 or higher immediately to apply the necessary path validation and security controls.

Proactive Monitoring: Monitor server logs for unusual file write operations, particularly requests directed at the music/playlists/update API, and audit the Python site-packages directory for unauthorized files.

Compensating Controls: Restrict network access to the Music Assistant interface to trusted IP ranges via firewall rules and ensure the service is running with the least privilege necessary rather than as root.

Public Exploit Available: Unknown

Organizations utilizing Music Assistant must prioritize upgrading to version 2.7.0 to eliminate this critical vulnerability. Given the ease of exploitation and the potential for full system compromise, delaying this update significantly increases the risk of unauthorized access and remote code execution.