CVE
server remote code execution in JSON-RPC API
Music Assistant server 2.7.11 and earlier are affected, and any authenticated user regardless of role can reach the flaw via WebSocket or REST. Fixed in 2.8.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.8.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Music Assistant server version 2.7.11 or earlier (affected versions <= 2.7.11). Attacker must have a valid authenticated account (any role) to reach the commands via WebSocket /ws or REST /api.
Summary
Music Assistant server has a flaw that lets any logged-in user, regardless of role, run arbitrary Python code with the server process's privileges. An attacker on an adjacent network can trigger it by sending crafted requests to the WebSocket or JSON-RPC API. An attacker could use this to read secrets and configuration, alter library data, and take control of the application container, and the flaw works on default installations.
Original description
Music Assistant is an open-source media library manager that integrates streaming services with connected speakers. Prior to 2.8.0, parse_arguments() passes the caller-controlled return_type parameter for config/core/get_value, config/providers/get_value, and config/players/get_value to parse_value() and Python eval() when resolving type parameters in music_assistant/helpers/api.py. Any authenticated user, regardless of role, can reach these commands through the WebSocket /ws endpoint or the REST JSON-RPC /api endpoint, causing arbitrary Python code to run with the Music Assistant server process privileges before command-handler validation, even if the request later fails. A default installation requires no special configuration, and compromise can expose secrets and configuration, alter library data, and control the application container. This issue is fixed in version 2.8.0.
Who should check
Teams running Music Assistant server 2.7.11 or earlier, including Home Assistant app installs and Docker deployments with multiple user accounts.
“Affected versions <= 2.7.11”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8/10CVSS 8.0
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Music Assistant server version 2.7.11 or earlier (affected versions <= 2.7.11). Attacker must have a valid authenticated account (any role) to reach the commands via WebSocket /ws or REST /api.Upgrade to a fixed version: 2.8.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-73971 (Music Assistant: Remote Code Execution by authenticated user), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-73971 (entry last updated 2026-11-18):
Affected:
- music-assistant server: fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Music Assistant server version 2.7.11 or earlier (affected versions <= 2.7.11). (source: https://github.com/music-assistant/server/security/advisories/GHSA-cjp7-8r57-vc8f)
- Attacker must have a valid authenticated account (any role) to reach the commands via WebSocket /ws or REST /api. (source: https://github.com/music-assistant/server/security/advisories/GHSA-cjp7-8r57-vc8f)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: adjacent access, low-privilege login, no user action.
CISA KEV: CVE-2026-73971 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-73971 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/music-assistant/server/security/advisories/GHSA-cjp7-8r57-vc8f
- https://github.com/music-assistant/server/pull/3271
- https://github.com/music-assistant/server/commit/c7408625bdaa08bdd4419255fccb1c7f82828d26
- https://github.com/music-assistant/server/commit/d79ffd1e393eacc9d9402eaa26ff50d9618b247b
- https://github.com/music-assistant/server/releases/tag/2.8.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-73971
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-73971"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- music-assistant server
fixed in 2.8.0
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · music-assistant/server · Advisory GHSA-cjp7-8r57-vc8f |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-73971 |
| Record | NVD · CVE-2026-73971 |
| Other links 4 | |
| Repository | GitHub · music-assistant/server · Pull request #3271 |
| Repository | GitHub · music-assistant/server · Commit c7408625 |
| Repository | GitHub · music-assistant/server · Commit d79ffd1e |
| Repository | GitHub · music-assistant/server · Release 2.8.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-73971
Is CVE-2026-73971 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Any authenticated Music Assistant user, regardless of role, can run arbitrary Python code with the privileges of the Music Assistant server process. That could allow theft of secrets, modification of library data, and control of the application container.Source: github.com
Which versions are affected by CVE-2026-73971?
server: before 2.8.0.Source: cve.now feed data
Am I affected, and how do I check?
The affected versions are Music Assistant server 2.7.11 and earlier. To check a installation, look at the server version it reports, since the fixed range starts at 2.8.0. The flaw requires a valid authenticated account reaching the commands through WebSocket /ws or REST /api.Source: github.com
How do I fix CVE-2026-73971?
Upgrade the Music Assistant server to 2.8.0 or later, which is the fixed version listed for this vulnerability.Source: github.com