CVE-2026-10595

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM 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(medium)
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
41%
KEV
Not listed

Published

August 9, 2026

Last Modified

September 3, 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 20× in last 7d / 100× 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.

Showing the most recent 100 of 148 total refreshes for this CVE.

  1. 2026-09-19 06:39 UTCEG score recompute
  2. 2026-09-19 06:39 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 17:25 UTCGHSA enrichment
  5. 2026-09-18 04:05 UTCEG score recompute
  6. 2026-09-18 04:05 UTCGHSA enrichment
  7. 2026-09-17 15:08 UTCGHSA enrichment
  8. 2026-09-17 00:52 UTCEG score recompute
  9. 2026-09-17 00:52 UTCGHSA enrichment
  10. 2026-09-16 05:14 UTCEPSS rescore
  11. 2026-09-16 02:46 UTCGHSA enrichment
  12. 2026-09-15 06:32 UTCEG score recompute
  13. 2026-09-15 06:32 UTCGHSA enrichment
  14. 2026-09-14 16:53 UTCGHSA enrichment
  15. 2026-09-14 03:57 UTCEG score recompute
  16. 2026-09-14 03:57 UTCGHSA enrichment
  17. 2026-09-13 16:46 UTCEPSS rescore
  18. 2026-09-13 15:01 UTCGHSA enrichment
  19. 2026-09-13 01:55 UTCEG score recompute
  20. 2026-09-13 01:55 UTCGHSA enrichment
  21. 2026-09-12 15:00 UTCEPSS rescore
  22. 2026-09-12 12:59 UTCGHSA enrichment
  23. 2026-09-12 00:03 UTCEG score recompute
  24. 2026-09-12 00:03 UTCGHSA enrichment
  25. 2026-09-11 14:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:45 UTCGHSA enrichment
  2. 2026-09-11 09:43 UTCEG score recompute
  3. 2026-09-11 09:43 UTCGHSA enrichment
  4. 2026-09-11 09:36 UTCEPSS rescore
  5. 2026-09-10 20:46 UTCEG score recompute
  6. 2026-09-10 20:46 UTCGHSA enrichment
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-10 07:50 UTCGHSA enrichment
  9. 2026-09-09 18:54 UTCGHSA enrichment
  10. 2026-09-09 05:58 UTCEG score recompute
  11. 2026-09-09 05:58 UTCGHSA enrichment
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-08 07:26 UTCEG score recompute
  14. 2026-09-08 07:26 UTCGHSA enrichment
  15. 2026-09-07 17:37 UTCEG score recompute
  16. 2026-09-07 17:37 UTCGHSA enrichment
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 18:01 UTCEG score recompute
  19. 2026-09-06 18:01 UTCGHSA enrichment
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-06 05:03 UTCGHSA enrichment
  22. 2026-09-05 16:07 UTCEG score recompute
  23. 2026-09-05 16:07 UTCGHSA enrichment
  24. 2026-09-05 02:17 UTCEG score recompute
  25. 2026-09-05 02:17 UTCGHSA enrichment
  26. 2026-09-04 08:33 UTCEG score recompute
  27. 2026-09-04 08:33 UTCGHSA enrichment
  28. 2026-09-04 05:06 UTCEPSS rescore
  29. 2026-09-03 18:06 UTCGHSA enrichment
  30. 2026-09-03 17:14 UTCGHSA enrichment
  31. 2026-09-03 03:58 UTCEG score recompute
  32. 2026-09-03 03:58 UTCGHSA enrichment
  33. 2026-09-02 14:11 UTCEPSS rescore
  34. 2026-09-02 06:41 UTCGHSA enrichment
  35. 2026-09-01 17:36 UTCEG score recompute
  36. 2026-09-01 17:36 UTCGHSA enrichment
  37. 2026-09-01 13:53 UTCEPSS rescore
  38. 2026-09-01 04:39 UTCEPSS rescore
  39. 2026-08-31 22:25 UTCGHSA enrichment
  40. 2026-08-31 01:08 UTCEG score recompute
  41. 2026-08-31 01:08 UTCGHSA enrichment
  42. 2026-08-30 19:17 UTCEPSS rescore
  43. 2026-08-30 12:12 UTCEG score recompute
  44. 2026-08-30 12:12 UTCGHSA enrichment
  45. 2026-08-30 01:21 UTCEPSS rescore
  46. 2026-08-29 23:16 UTCGHSA enrichment
  47. 2026-08-29 10:15 UTCEG score recompute
  48. 2026-08-29 10:15 UTCGHSA enrichment
  49. 2026-08-28 21:40 UTCEPSS rescore
  50. 2026-08-28 01:43 UTCEG score recompute
  51. 2026-08-28 01:43 UTCGHSA enrichment
  52. 2026-08-27 14:24 UTCEPSS rescore
  53. 2026-08-27 12:47 UTCGHSA enrichment
  54. 2026-08-26 23:51 UTCEG score recompute
  55. 2026-08-26 23:51 UTCGHSA enrichment
  56. 2026-08-26 10:54 UTCGHSA enrichment
  57. 2026-08-25 21:58 UTCEG score recompute
  58. 2026-08-25 21:58 UTCGHSA enrichment
  59. 2026-08-25 13:48 UTCEPSS rescore
  60. 2026-08-25 08:59 UTCGHSA enrichment
  61. 2026-08-24 20:04 UTCEG score recompute
  62. 2026-08-24 20:04 UTCGHSA enrichment
  63. 2026-08-24 07:06 UTCGHSA enrichment
  64. 2026-08-23 18:10 UTCGHSA enrichment
  65. 2026-08-23 05:14 UTCEG score recompute
  66. 2026-08-23 05:14 UTCGHSA enrichment
  67. 2026-08-23 00:19 UTCEPSS rescore
  68. 2026-08-22 16:19 UTCGHSA enrichment
  69. 2026-08-22 03:23 UTCEG score recompute
  70. 2026-08-22 03:23 UTCGHSA enrichment
  71. 2026-08-21 23:48 UTCEPSS rescore
  72. 2026-08-21 14:27 UTCGHSA enrichment
  73. 2026-08-21 01:31 UTCEG score recompute
  74. 2026-08-21 01:31 UTCGHSA enrichment
  75. 2026-08-20 22:55 UTCEPSS rescore

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 September 3, 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 58.7% 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.