Skip to main content
VulnerabilityPublished Updated

CVE-2024-5443: Remote Code Execution via path traversal bypass in lollms

Affects lollmsSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 9.5.1 as a priority.

Data as of 16 Nov 2026, 16:50 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 9.5.1
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade lollms to 9.5.1.

Affected software

ProductAffectedFixed in
PyPIlollmsAffected
  • >=5.9.0 <9.5.1
Fixed in
  • 9.5.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and the vulnerability is fixed in lollms version 9.5.1. Users should upgrade to version 9.5.1 or later to remediate this issue. No additional mitigations are specified by the vendor advisory.

Description

A critical remote code execution vulnerability (CVE-2024-5443) exists in lollms versions 5.9.0 up to but not including 9.5.1. The flaw is due to a path traversal bypass in the /mount_extension endpoint, where insufficient input sanitization of parameters allows attackers to escape the intended directory structure. This can lead to execution of arbitrary code via a crafted config.yaml file and the triggering of __init__.py in an attacker-controlled path. The issue is fixed in version 9.5.1.

References

Community reviews

Loading reviews…