# CVE-2026-103395: LightLLM through 1.2.0 Unauthenticated Remote Code Execution via Visual-Only RPyC Service

> Attackers can execute arbitrary code on LightLLM visual-only deployments by sending malicious serialized objects to an unauthenticated RPyC service.

- **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:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-mw2v-h3wh-mp72

## What is CVE-2026-103395?

CVE-2026-103395 is a critical unsafe deserialization vulnerability in ModelTC LightLLM, published on 30 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 visual_only deployments expose an unauthenticated RPyC service with allow_pickle enabled that deserializes attacker-supplied arguments in the remote_infer_images method. Attackers can reach the visual RPyC port and pass objects with __reduce__ methods to execute arbitrary code with service account privileges.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-103395 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103395 is a critical unsafe deserialization vulnerability in ModelTC LightLLM, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-103395 exists.

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

## Sources

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

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