CVE-2024-3429

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 39% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 28%CVSS: 9.8Exploit: NoneExposed: 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 the parisneo/lollms application, specifically within the sanitize_path_from_endpoint and sanitize_path functions in lollms_core\lollms\security.py. This vulnerability allows for arbitrary file reading when the application is running on Windows. The issue arises due to insufficient sanitization of user-supplied input, enabling attackers to bypass the path traversal protection mechanisms by crafting malicious input. Successful exploitation could lead to unauthorized access to sensitive files, information disclosure, and potentially a denial of service (DoS) condition by including numerous large or resource-intensive files. This vulnerability affects the latest version prior to 9.6.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
97.9%
KEV
Not listed

Published

June 6, 2024

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated May 26, 2026
No patch confirmed yet.
generic

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

https://huntr.com/bounties/fd8f50c8-17f0-40be-a2c6-bb8d80f7c409

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
lollms1.1.10 ... 9.3.0 (263 versions)9.5.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 36× 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-07-11 08:26 UTCEPSS rescore
  2. 2026-07-11 08:26 UTCEPSS rescore
  3. 2026-07-09 19:09 UTCEPSS rescore
  4. 2026-07-08 15:14 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-04 06:30 UTCEPSS rescore
  8. 2026-07-01 15:05 UTCEPSS rescore
  9. 2026-06-30 23:21 UTCEPSS rescore
  10. 2026-06-30 23:21 UTCEPSS rescore
  11. 2026-06-29 14:05 UTCEPSS rescore
  12. 2026-06-28 14:06 UTCEPSS rescore
  13. 2026-06-28 14:06 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-27 03:07 UTCEPSS rescore
  17. 2026-06-27 03:07 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:04 UTCEPSS rescore
  20. 2026-06-24 14:04 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-23 21:32 UTCEPSS rescore
  23. 2026-06-21 01:58 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-19 19:25 UTCEPSS rescore
Show 47 more
  1. 2026-06-19 19:25 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 17:51 UTCEPSS rescore
  4. 2026-06-17 17:52 UTCEPSS rescore
  5. 2026-06-16 17:52 UTCEPSS rescore
  6. 2026-06-16 17:52 UTCEPSS rescore
  7. 2026-06-15 17:47 UTCEPSS rescore
  8. 2026-06-14 23:16 UTCEPSS rescore
  9. 2026-06-13 22:59 UTCEPSS rescore
  10. 2026-06-13 22:59 UTCEPSS rescore
  11. 2026-06-12 23:11 UTCEPSS rescore
  12. 2026-06-11 13:59 UTCEPSS rescore
  13. 2026-06-10 22:17 UTCEPSS rescore
  14. 2026-06-10 13:21 UTCEPSS rescore
  15. 2026-06-08 14:16 UTCEPSS rescore
  16. 2026-06-07 15:24 UTCEPSS rescore
  17. 2026-06-07 15:24 UTCEPSS rescore
  18. 2026-06-06 13:46 UTCEPSS rescore
  19. 2026-06-06 13:46 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-02 20:12 UTCEPSS rescore
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-05-31 22:30 UTCEPSS rescore
  30. 2026-05-31 22:30 UTCEPSS rescore
  31. 2026-05-31 00:15 UTCEPSS rescore
  32. 2026-05-31 00:15 UTCEPSS rescore
  33. 2026-05-29 13:43 UTCEPSS rescore
  34. 2026-05-28 13:44 UTCEPSS rescore
  35. 2026-05-28 13:44 UTCEPSS rescore
  36. 2026-05-28 13:44 UTCEPSS rescore
  37. 2026-05-27 13:40 UTCEPSS rescore
  38. 2026-05-27 13:40 UTCEPSS rescore
  39. 2026-05-27 13:40 UTCEPSS rescore
  40. 2026-05-26 13:43 UTCEPSS rescore
  41. 2026-05-26 13:43 UTCEPSS rescore
  42. 2026-05-26 07:18 UTCEPSS rescore
  43. 2026-05-26 07:18 UTCEPSS rescore
  44. 2026-05-26 07:18 UTCEPSS rescore
  45. 2026-05-24 00:31 UTCEG score recompute
  46. 2026-05-24 00:31 UTCEG score recompute
  47. 2026-05-24 00:22 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-3429?
CVE-2024-3429 is a critical vulnerability published on June 6, 2024. A path traversal vulnerability exists in the parisneo/lollms application, specifically within the sanitizepathfromendpoint and sanitizepath functions in lollms_core\lollms\security.py. This vulnerability allows for arbitrary file reading when the application is running on Windows. The issue arises…
When was CVE-2024-3429 disclosed?
CVE-2024-3429 was first published in the National Vulnerability Database on June 6, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-3429 actively exploited?
CVE-2024-3429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-3429?
CVE-2024-3429 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-3429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-3429, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-3429

Explore →

Is Your Infrastructure Affected by CVE-2024-3429?

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

Start Free Scan →Browse All CVEs