yoshitomo-matsubara torchdistill up to 1.1.5 main_util.py load_ckpt src_ckpt deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 2.82 |
Summary
A vulnerability was found in yoshitomo-matsubara torchdistill up to 1.1.5. It has been classified as problematic. This vulnerability affects the function load_ckpt of the file torchdistill/common/main_util.py. The manipulation of the argument src_ckpt leads to deserialization.
This vulnerability is documented as CVE-2026-108947. The attack needs to be performed locally. Additionally, an exploit exists.
The project maintainer explains: "This is very similar to an internal report that GH auto-generated for the owner before, which I found tolerable for this project at that time. So I will close this as duplicate."
Details
A vulnerability was found in yoshitomo-matsubara torchdistill up to 1.1.5. It has been rated as problematic. This issue affects the function load_ckpt of the file torchdistill/common/main_util.py. The manipulation of the argument src_ckpt with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-108947. The exploitation is known to be easy. Attacking locally is a requirement. Technical details as well as a public exploit are known.
The exploit is available at github.com. It is declared as proof-of-concept. The project maintainer explains: "This is very similar to an internal report that GH auto-generated for the owner before, which I found tolerable for this project at that time. So I will close this as duplicate."
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/11/2026 Advisory disclosed10/11/2026 VulDB entry created
10/11/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 550
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-108947 (🔒)
GCVE (CVE): GCVE-0-2026-108947
GCVE (VulDB): GCVE-100-416771
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/11/2026 21:03Changes: 10/11/2026 21:03 (59)
Complete: 🔍
Submitter: Dem0
Cache ID: 216::103
Submit
Accepted
- Submit #997819: yoshitomo-matsubara torchdistill up to 1.1.5 Insecure Deserialization (by Dem0)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.