# CVE-2026-116073: Leon before commit 50df142 Path Traversal via /download model Command


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 25 Oct 2026
- **Also known as:** GHSA-5jhh-46x7-49hp

## What is CVE-2026-116073?

CVE-2026-116073 is a medium-severity vulnerability in leon-ai leon, published on 25 Oct 2026. 

### Official description

Leon before commit 50df142 contains a path traversal vulnerability in getModelFileNameFromURL() that allows attackers to write files outside the models directory via percent-encoded separators. Attackers can trick a user into running '/download model' with a crafted URL containing encoded '../' sequences to write attacker-controlled content to arbitrary paths writable by Leon.

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

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


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

No fix has been published for CVE-2026-116073 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116073 being exploited?

There is no known exploitation of CVE-2026-116073 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116073 is a medium-severity vulnerability in leon-ai leon, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116073 in the wild and no public exploit code.

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

## Sources

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

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