LM Studio before 0.4.22+1 Path Traversal via Model Downloader
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.4.22+1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
LM Studio, a desktop application for running AI models locally, is affected by a path traversal flaw in its model downloader. An attacker who tricks a user into downloading a specially crafted model repository could write files outside the intended models folder, planting configuration files that cause an attacker-supplied Python script to run every time the application starts.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
LM Studio before 0.4.22+1 contains a path traversal vulnerability in the model downloader's resolveDownloadRequest that allows attackers to write files outside the models directory using backslash-separated traversal filenames. Attackers can trick users into downloading a crafted model repository that plants a plugin manifest.json, install-state.json and mcp-bridge-config.json, running an attacker-supplied Python payload on every launch.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Element Labs LM Studio
fixed in 0.4.22+1
References 2
Questions about CVE-2026-119979
What does this mean?
A flaw in LM Studio's model downloader lets a crafted model repository write files outside the models directory. Those files can plant plugin and configuration files, and can run an attacker-supplied Python payload each time LM Studio starts.Source: vulncheck.com
Am I affected, and how do I check?
LM Studio versions before 0.4.22+1 are affected. To check an install, look up the version shown in the LM Studio app about screen or the version in its installation details, and compare it with 0.4.22+1.Source: vulncheck.com
What should I do about it?
Upgrade LM Studio to 0.4.22+1 or later, which is the fixed version listed in the advisory data. Only download models from sources you trust until the upgrade is done.Source: vulncheck.com
Is it 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