Localai vulnerabilities
5 known vulnerabilities in Localai from Mudler. 5 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
mudler/localai: Improper Link Resolution Before File Access
mudler/LocalAI version 2.17.1 allows for arbitrary file write due to improper handling of automatic archive extraction. When model configurations specify additional files as archives (e.g., .tar), these archives are automatically extracted after downloading. T
- 8.8 High severity
mudler/localai: Improper Control of Generation of Code
mudler/localai version 2.17.1 is vulnerable to remote code execution. The vulnerability arises because the localai backend receives inputs not only from the configuration file but also from other inputs, allowing an attacker to upload a binary file and execute
- 9.8 Critical severity
mudler/localai: Improper Neutralization of Special Elements used in an OS Command
A command injection vulnerability exists in the mudler/localai version 2.14.0. The vulnerability arises from the application's handling of the backend parameter in the configuration file, which is used in the name of the initialized process. An attacker can ex
- 9.1 Critical severity
mudler/localai: Improper Limitation of a Pathname to a Restricted Directory
A path traversal vulnerability exists in mudler/localai version 2.14.0, where an attacker can exploit the `model` parameter during the model deletion process to delete arbitrary files. Specifically, by crafting a request with a manipulated `model` parameter, a
- 9.8 Critical severity
mudler/localai: Improper Neutralization of Special Elements used in an OS Command
A command injection vulnerability exists in the `TranscriptEndpoint` of mudler/localai, specifically within the `audioToWav` function used for converting audio files to WAV format for transcription. The vulnerability arises due to the lack of sanitization of u