CVE-2026-111925
Description
A flaw was found in Mopidy. A remote, unauthenticated attacker can access local files outside the configured media directories due to missing path containment checks in the file library component. By sending requests with manipulated file paths over network interfaces, an attacker can determine whether local files exist, inspect file metadata, and access unauthorized files on the host system.
Statement
Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery. For more information about this vulnerability and the products it affects, please see the linked references.
Mitigation
Disable the local file library extension or restrict network exposure to trusted interfaces.
1. To disable the file extension, edit the Mopidy configuration file (e.g., `/etc/mopidy/mopidy.conf`):
ini
[file]
enabled = false
2. Alternatively, restrict access to the HTTP/WebSocket port (default 6680) using `firewalld`:
bash
firewall-cmd --permanent --remove-port=6680/tcp
firewall-cmd --reload
3. Apply changes by restarting the service:
bash
systemctl restart mopidy
Warning: Restarting the Mopidy service will terminate active streaming sessions and disconnect connected clients. Disabling the file extension prevents indexing and playback of local files.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
