Local code execution via unsafe checkpoint deserialization
Published Apr 3, 2025 · Updated Apr 21, 2025
Unsafe deserialization in Chitu 0.1.0 allows local users to execute arbitrary code by supplying a malicious model checkpoint. backend.py passes ckpt_path and quant_ckpt_dir to torch.load without weights_only=True, allowing Python objects in .pt files to execute during loading. Exploitation requires low-privilege local access and control of a checkpoint path consumed by the inference process.
Summary
What happened
Unsafe deserialization in Chitu 0.1.0 allows local users to execute arbitrary code by supplying a malicious model checkpoint. backend.py passes ckpt_path and quant_ckpt_dir to torch.load without weights_only=True, allowing Python objects in .pt files to execute during loading. Exploitation requires low-privilege local access and control of a checkpoint path consumed by the inference process.
The record
- CVE
- CVE-2025-3165
- Published
- Apr 3, 2025
- Updated
- Apr 21, 2025
- Vendor
- PACMAN Group, Tsinghua University
- Product
- Chitu
- Classifications
- CWE-20, CWE-502, T1059.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Apr 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo