CVE-2026-10595

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-09. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

August 9, 2026

Last Modified

August 10, 2026

Advisory Details (2)

Auto-updated Aug 9, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/af3f40a3-38a1-49d8-a5ae-3d72b9b05b98
github_commit

commit 9bc6431ae7b7 (parisneo/lollms)

Fix landed in parisneo/lollms commit 9bc6431ae7b7 — awaiting tagged release

https://github.com/parisneo/lollms/commit/9bc6431ae7b708da76d51e7626a7cf48ff2b1d24

Vendor Advisories for CVE-2026-10595(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 12:35 UTCGHSA enrichment
  2. 2026-08-19 23:39 UTCEG score recompute
  3. 2026-08-19 23:39 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 10:43 UTCGHSA enrichment
  6. 2026-08-18 21:40 UTCEG score recompute
  7. 2026-08-18 21:40 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 08:23 UTCGHSA enrichment
  10. 2026-08-17 19:24 UTCEG score recompute
  11. 2026-08-17 19:24 UTCGHSA enrichment
  12. 2026-08-17 05:44 UTCGHSA enrichment
  13. 2026-08-16 16:40 UTCEG score recompute
  14. 2026-08-16 16:40 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 03:42 UTCEG score recompute
  17. 2026-08-16 03:42 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 14:47 UTCGHSA enrichment
  20. 2026-08-15 01:51 UTCEG score recompute
  21. 2026-08-15 01:51 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 12:55 UTCGHSA enrichment
  24. 2026-08-14 00:00 UTCEG score recompute
  25. 2026-08-14 00:00 UTCGHSA enrichment
Show 23 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 11:04 UTCGHSA enrichment
  3. 2026-08-12 22:09 UTCEG score recompute
  4. 2026-08-12 22:09 UTCGHSA enrichment
  5. 2026-08-12 13:50 UTCEPSS rescore
  6. 2026-08-12 09:13 UTCGHSA enrichment
  7. 2026-08-11 20:17 UTCEG score recompute
  8. 2026-08-11 20:17 UTCGHSA enrichment
  9. 2026-08-11 13:42 UTCEPSS rescore
  10. 2026-08-11 07:21 UTCEG score recompute
  11. 2026-08-11 07:21 UTCGHSA enrichment
  12. 2026-08-10 23:59 UTCEPSS rescore
  13. 2026-08-10 18:26 UTCEG score recompute
  14. 2026-08-10 18:26 UTCGHSA enrichment
  15. 2026-08-10 17:35 UTCEG score recompute
  16. 2026-08-10 17:35 UTCGHSA enrichment
  17. 2026-08-10 06:12 UTCGHSA enrichment
  18. 2026-08-09 17:16 UTCEG score recompute
  19. 2026-08-09 17:16 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 04:21 UTCEG score recompute
  22. 2026-08-09 04:10 UTCEG score recompute
  23. 2026-08-09 04:10 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10595?
CVE-2026-10595 is a high vulnerability published on August 9, 2026. 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…
When was CVE-2026-10595 disclosed?
CVE-2026-10595 was first published in the National Vulnerability Database on August 9, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10595 actively exploited?
CVE-2026-10595 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.8% of all scored CVEs.
What is the CVSS score of CVE-2026-10595?
CVE-2026-10595 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10595?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10595, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10595

Explore →

Is Your Infrastructure Affected by CVE-2026-10595?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs