# CVE-2025-3165: thu-pacman chitu backend.py torch.load deserialization

> A local attacker can execute arbitrary code via unsafe deserialization in the chitu library's backend module.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2025
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-j2pg-qhxw-x7gx

## What is CVE-2025-3165?

CVE-2025-3165 is a medium-severity unsafe deserialization vulnerability in thu-pacman chitu, published on 3 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in thu-pacman chitu 0.1.0. This affects the function torch.load of the file chitu/chitu/backend.py. The manipulation of the argument ckpt_path/quant_ckpt_dir leads to deserialization. An attack has to be approached locally.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-3165?


## How do I fix CVE-2025-3165?

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

## Is CVE-2025-3165 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3165 and fix it if it is affected.

What it is: CVE-2025-3165 is a medium-severity unsafe deserialization vulnerability in thu-pacman chitu, published on 3 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3165 in the wild and no public exploit code.

Affected product: thu-pacman chitu. 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-2025-3165/ (Markdown: https://insights.sbomify.com/CVE-2025-3165/index.md)
```

## Sources

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

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