# CVE-2026-108947: yoshitomo-matsubara torchdistill main_util.py load_ckpt deserialization

> Local attackers can achieve code execution via unsafe deserialization in the load_ckpt function of the torchdistill library.

- **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/E:P`)
- **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:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-m93m-2x62-w23p

## What is CVE-2026-108947?

CVE-2026-108947 is a medium-severity unsafe deserialization vulnerability in yoshitomo-matsubara torchdistill, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in yoshitomo-matsubara torchdistill up to 1.1.5. This affects the function load_ckpt of the file torchdistill/common/main_util.py. Executing a manipulation of the argument src_ckpt can lead to deserialization. The attack needs to be launched locally. The exploit has been published and may be used. 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."

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

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


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

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

## Is CVE-2026-108947 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108947 is a medium-severity unsafe deserialization vulnerability in yoshitomo-matsubara torchdistill, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108947 exists.

Affected product: yoshitomo-matsubara torchdistill. 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-108947/ (Markdown: https://insights.sbomify.com/CVE-2026-108947/index.md)
```

## Sources

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

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