# CVE-2026-41318: Cross-site scripting in anything-llm

> Attackers can inject malicious scripts via LLM-generated chart captions, leading to stored XSS and potential account takeover in shared workspaces.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-4q6m-qh3w-9gf5

## What is CVE-2026-41318?

CVE-2026-41318 is a medium-severity cross-site scripting vulnerability in Mintplexlabs Anythingllm, published on 24 Apr 2026. Any signed-in user can exploit it over the network, 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. Prior to version 1.12.1, AnythingLLM's in-chat markdown renderer has an unsafe custom rule for images that interpolates the markdown image's `alt` text into an HTML `alt="..."` attribute without any HTML encoding. Every call-site in the app wraps `renderMarkdown(...)` with `DOMPurify.sanitize(...)` as defense-in-depth — except the `Chartable` component, which renders chart captions with no sanitization. The chart caption is the natural-language text the LLM emits around a `create-chart` tool call, so any attacker who can influence the LLM's output — most cheaply via indirect prompt injection in a shared workspace document, or directly if they can create a chart record in a multi-user workspace — can trigger stored DOM-level XSS in every other user's browser when they open that conversation. AnythingLLM chat history is loaded server-side via `GET /api/workspace/:slug/chats` and rendered directly into the chat UI. Version 1.12.1 contains a patch for this issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine), CWE-116 (Improper Encoding or Escaping of Output)

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

It affects 1 product.


Products: Mintplexlabs Anythingllm.

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

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

## Is CVE-2026-41318 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41318 exists.

## 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-2026-32626](https://insights.sbomify.com/CVE-2026-32626/): AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection (critical 9.7)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41318 is a medium-severity cross-site scripting vulnerability in Mintplexlabs Anythingllm, published on 24 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41318 exists.

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-41318/ (Markdown: https://insights.sbomify.com/CVE-2026-41318/index.md)
```

## Sources

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

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