# CVE-2026-32626: AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection

> Attackers can achieve remote code execution on the host OS via XSS in the chat rendering pipeline due to insecure Electron configuration and lack of sanitization.

- **Severity:** Critical 9.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-rrmw-2j6x-4mf2

## What is CVE-2026-32626?

CVE-2026-32626 is a critical cross-site scripting vulnerability in Mintplexlabs Anythingllm, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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().

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-32626?

It affects 1 product.


Products: Mintplexlabs Anythingllm.

## How do I fix CVE-2026-32626?

No fix has been published for CVE-2026-32626 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32626 being exploited?

There is no known exploitation of CVE-2026-32626 in the wild and no public exploit code.

## Other vulnerabilities in Mintplexlabs Anythingllm

- [CVE-2024-3025](https://insights.sbomify.com/CVE-2024-3025/): Path Traversal in mintplex-labs/anything-llm (critical 9.9)
- [CVE-2024-0455](https://insights.sbomify.com/CVE-2024-0455/): SSRF on AWS deployed instances of AnythingLLM via /metadata (critical 9.9)
- [CVE-2024-3104](https://insights.sbomify.com/CVE-2024-3104/): Remote Code Execution in mintplex-labs/anything-llm (critical 9.6)
- [CVE-2024-3149](https://insights.sbomify.com/CVE-2024-3149/): SSRF in mintplex-labs/anything-llm (critical 9.6)
- [CVE-2024-0765](https://insights.sbomify.com/CVE-2024-0765/): Default user role exporting save state of instance (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32626 and fix it if it is affected.

What it is: CVE-2026-32626 is a critical cross-site scripting vulnerability in Mintplexlabs Anythingllm, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32626 in the wild and no public exploit code.

Affected product: Mintplexlabs Anythingllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32626/ (Markdown: https://insights.sbomify.com/CVE-2026-32626/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32626
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32626
- OSV: https://osv.dev/vulnerability/CVE-2026-32626

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32626/
Summaries are generated and may contain mistakes; the official description above is the record.