# CVE-2026-96560: LightLLM through 1.2.0 Unauthenticated Remote Code Execution via NCCL PD RPyC Control Channel

> Attackers can execute arbitrary code by sending malicious pickled objects to an unauthenticated RPyC channel when NCCL PD mode is enabled.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-849v-g89f-q67r

## What is CVE-2026-96560?

CVE-2026-96560 is a critical unsafe deserialization vulnerability in ModelTC LightLLM, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LightLLM through 1.2.0 contains a remote code execution vulnerability in the KV-transfer worker when started with --pd_trans_mode nccl, which exposes an unauthenticated RPyC control channel that deserializes attacker-supplied data. Attackers can send malicious pickled objects to the exposed RPyC ThreadedServer to execute arbitrary code with the privileges of the LightLLM service account.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-96560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96560 is a critical unsafe deserialization vulnerability in ModelTC LightLLM, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96560 in the wild and no public exploit code.

Affected product: ModelTC LightLLM. 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-96560/ (Markdown: https://insights.sbomify.com/CVE-2026-96560/index.md)
```

## Sources

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

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