# CVE-2026-26975: Music Assistant Server Path Traversal in Playlist Update API Allows Remote Code Execution

> Unauthenticated attackers can exploit path traversal in the playlist API to write malicious files, achieving remote code execution on Music Assistant Server installations.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-7jcc-p6xr-835j

## What is CVE-2026-26975?

CVE-2026-26975 is a high-severity path traversal vulnerability in music-assistant server, published on 20 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-26975?

It affects 1 product.


Products: Music-Assistant Music Assistant Server.

## How do I fix CVE-2026-26975?

No fix has been published for CVE-2026-26975 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26975 being exploited?

There is no known exploitation of CVE-2026-26975 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26975 and fix it if it is affected.

What it is: CVE-2026-26975 is a high-severity path traversal vulnerability in music-assistant server, published on 20 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26975 in the wild and no public exploit code.

Affected product: music-assistant server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26975/ (Markdown: https://insights.sbomify.com/CVE-2026-26975/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26975
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26975
- OSV: https://osv.dev/vulnerability/CVE-2026-26975

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26975/
Summaries are generated and may contain mistakes; the official description above is the record.