# CVE-2025-4701: VITA-MLLM Freeze-Omni utils.py torch.load deserialization

> An attacker can execute arbitrary code by exploiting unsafe deserialization in the torch.load function within the VITA-MLLM Freeze-Omni 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`)
- **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:** 15 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-hp48-2c8c-rm54

## What is CVE-2025-4701?

CVE-2025-4701 is a medium-severity unsafe deserialization vulnerability in VITA-MLLM Freeze-Omni, published on 15 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, has been found in VITA-MLLM Freeze-Omni up to 20250421. This issue affects the function torch.load of the file models/utils.py. The manipulation of the argument path leads to deserialization. It is possible to launch the attack on the local host.

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

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


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

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

## Is CVE-2025-4701 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4701 is a medium-severity unsafe deserialization vulnerability in VITA-MLLM Freeze-Omni, published on 15 May 2025. 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-2025-4701 exists.

Affected product: VITA-MLLM Freeze-Omni. 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-4701/ (Markdown: https://insights.sbomify.com/CVE-2025-4701/index.md)
```

## Sources

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

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