# CVE-2026-32617: AnythingLLM Permissable CORS policy

> AnythingLLM desktop allows unauthenticated access and permissive CORS on default installs, enabling local network attackers to read or modify data.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L`)
- **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-24qj-pw4h-3jmm

## What is CVE-2026-32617?

CVE-2026-32617 is a high-severity 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, On default installations where no password or API key has been configured, all HTTP endpoints and the agent WebSocket lack authentication, and the server's CORS policy accepts any origin. AnythingLLM Desktop binds to 127.0.0.1 (loopback) by default. Modern browsers (Chrome, Edge, Firefox) implement Private Network Access (PNA). This explicitly blocks public websites from making requests to local IP addresses. Exploitation is only viable from within the same local network (LAN) due to browser-level blocking of public-to-private requests.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Mintplexlabs Anythingllm.

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

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

## Is CVE-2026-32617 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32617 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-32617 and fix it if it is affected.

What it is: CVE-2026-32617 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32617 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-32617/ (Markdown: https://insights.sbomify.com/CVE-2026-32617/index.md)
```

## Sources

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

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