Skip to main content
VulnerabilityPublished Updated

CVE-2026-1116: parisneo/lollms · Cross-site Scripting

Affects parisneo/lollmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2.2.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Apr 2026

  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 30 Oct 2026.

What to do

Upgrade parisneo/lollms to 2.2.0.

Affected software

ProductAffectedFixed in
parisneoparisneo/lollmsAffected
  • ≥ unspecified, < 2.2.0
Fixed in–
GitHubparisneo/lollmspkg:github/parisneo/lollmsOther threatsAffected
  • <2.2.0
Fixed in
  • 2.2.0

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

AI-suggested

If you cannot patch yet, users should exercise caution when handling untrusted input in the affected component. Avoid deserializing untrusted data or implement manual sanitization as a temporary mitigation.

Description

A Cross-site Scripting (XSS) vulnerability was identified in the `from_dict` method of the `AppLollmsMessage` class in parisneo/lollms prior to version 2.2.0. The vulnerability arises from the lack of sanitization or HTML encoding of the `content` field when deserializing user-provided data. This allows an attacker to inject malicious HTML or JavaScript payloads, which can be executed in the context of another user's browser. Exploitation of this vulnerability can lead to account takeover, session hijacking, or wormable attacks.

References

Community reviews

Loading reviews…