# CVE-2026-75128: Langchain-Chatchat through 0.3.1.3 Unauthenticated RCE via /tools/call Endpoint


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-5rx2-xp53-9x5r

## What is CVE-2026-75128?

CVE-2026-75128 is a critical vulnerability in chatchat-space Langchain-Chatchat, published on 20 Oct 2026. 

### Official description

Langchain-Chatchat through 0.3.1.3 exposes a POST /tools/call API endpoint that invokes any registered tool by name without authentication, leaving the always-registered shell tool callable. Remote attackers can send a single request naming the shell tool to execute arbitrary OS commands as the server user (root in the shipped Docker image).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-75128 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75128 is a critical vulnerability in chatchat-space Langchain-Chatchat, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75128 exists.

Affected product: chatchat-space Langchain-Chatchat. 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-75128/ (Markdown: https://insights.sbomify.com/CVE-2026-75128/index.md)
```

## Sources

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

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