# CVE-2026-111925: Mopidy before 4.0.5 Path Traversal via File Backend library.lookup

> Unauthenticated attackers can exploit path traversal in Mopidy to read local file metadata and play out-of-sandbox files via JSON-RPC or WebSocket.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-111925, GHSA-p8f3-3m4r-p796, UBUNTU-CVE-2026-111925

## What is CVE-2026-111925?

CVE-2026-111925 is a medium-severity path traversal vulnerability in Mopidy, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mopidy before 4.0.5 contains a path traversal vulnerability that allows unauthenticated clients to access local files outside file/media_dirs because FileLibraryProvider.lookup() lacks a containment check. Attackers can call core.library.lookup or core.tracklist.add over JSON-RPC or WebSocket with file:// URIs to probe file existence, read tag metadata, and play out-of-sandbox files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

Upgrade to a fixed version.

## Is CVE-2026-111925 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111925 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111925 is a medium-severity path traversal vulnerability in Mopidy, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111925 exists.

Affected product: Mopidy. 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-111925/ (Markdown: https://insights.sbomify.com/CVE-2026-111925/index.md)
```

## Sources

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

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