Skip to main content
VulnerabilityPublished Updated

CVE-2026-32626: Mintplex-Labs anything-llm · Cross-site Scripting

Affects Mintplex-Labs anything-llmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.7 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.7Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Mar 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

Affected software

ProductAffectedFixed in
Mintplex-Labsanything-llmAffected
  • <=1.11.1
Fixed in–
GitHubmintplex-labs/anything-llmpkg:github/mintplex-labs/anything-llmOther threatsAffected
  • <=1.11.1
Fixed in–

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

AI-suggested

To mitigate CVE-2026-32626, organizations should immediately upgrade AnythingLLM Desktop to a version patched by Mintplex-Labs once available. Until a patch is released, users should consider disabling or restricting the chat feature that processes untrusted content. Implementing strict input validation and output encoding in the markdown-it image renderer is critical; specifically, HTML entity escaping must be applied to all user-controlled content inserted into HTML attributes. The PromptReply component should be refactored to apply DOMPurify sanitization consistently, matching the approach used in HistoricalMessage. Electron application security best practices must be enforced, including enabling context isolation, disabling nodeIntegration where possible, and applying Content Security Policy (CSP) headers to limit script execution. Monitoring chat inputs for suspicious payloads and employing runtime application self-protection (RASP) can provide additional defense layers. Organizations should also conduct thorough code audits of Electron apps and educate developers on secure rendering practices to prevent similar vulnerabilities.

Description

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. In 1.11.1 and earlier, AnythingLLM Desktop contains a Streaming Phase XSS vulnerability in the chat rendering pipeline that escalates to Remote Code Execution on the host OS due to insecure Electron configuration. This works with default settings and requires no user interaction beyond normal chat usage. The custom markdown-it image renderer in frontend/src/utils/chat/markdown.js interpolates token.content directly into the alt attribute without HTML entity escaping. The PromptReply component renders this output via dangerouslySetInnerHTML without DOMPurify sanitization — unlike HistoricalMessage which correctly applies DOMPurify.sanitize().

References

Community reviews

Loading reviews…