CVE-2026-10595

HighCVSS 7.5

Published: 09/08/2026(UTC)Updated: 10/08/2026(UTC)Translated: 09/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.49%

40th percentile - higher than 40% of all known CVEs

Summary

A path traversal vulnerability exists in parisneo/lollms version 2.1.0, in the SPA catch-all route in `backend/routers/ui.py`. Improper handling of user-controlled path input, which is directly joined into a filesystem path without sanitization, allows an unauthenticated attacker to read arbitrary files on the server. This issue has been resolved in version 3.

Risk Assessment

An attacker can read arbitrary files on the server, including configuration files, user data, or secrets, potentially leading to confidentiality breaches and further attacks.

Recommendation

It is recommended to immediately upgrade to version 3 or later, which includes the fix eliminating the vulnerability.

Other vulnerabilities in parisneo/lollms

CVE-2026-1163Medium
The latest version of parisneo/lollms contains an insufficient session expiration vulnerability. The application fails to invalidate active sessions after a password reset, allowing an attacker to continue using an old session token. This is due to the absence of logic to reject requests after inactivity and the excessively long default session duration of 31 days. Attackers can maintain persistent access to a compromised account even after the victim resets their password.

Original NVD description (English source)

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.