# CVE-2026-10595: Path Traversal Vulnerability in parisneo/lollms

> An unauthenticated attacker can read arbitrary files on the server via path traversal in the SPA catch-all route of lollms.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-37c2-pxv8-c2mx

## What is CVE-2026-10595?

CVE-2026-10595 is a high-severity path traversal vulnerability in parisneo/lollms, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability exists in parisneo/lollms version 2.1.0, specifically in the SPA catch-all route implemented in `backend/routers/ui.py`. The vulnerability arises from the improper handling of user-controlled path input, which is directly joined into a filesystem path without sanitization or containment checks. URL-encoded dot-dot sequences (`%2e%2e`) bypass Starlette's built-in path normalization and are resolved by Python's `pathlib`, allowing an unauthenticated attacker to read arbitrary files on the server. This issue has been resolved in version 3.

Weakness: CWE-23 (Relative Path Traversal)

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


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

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

## Is CVE-2026-10595 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10595 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10595 is a high-severity path traversal vulnerability in parisneo/lollms, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10595 exists.

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

## Sources

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

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