# CVE-2025-50472: Deserialization in n/a

> Attackers can execute arbitrary code by tricking users into loading malicious serialized model files in the ms-swift library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2025
- **Updated:** 1 Aug 2025
- **Also known as:** GHSA-qgm9-fp3r-vm5v

## What is CVE-2025-50472?

CVE-2025-50472 is a critical unsafe deserialization vulnerability in n/a, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The modelscope/ms-swift library thru 2.6.1 is vulnerable to arbitrary code execution through deserialization of untrusted data within the `load_model_meta()` function of the `ModelFileSystemCache()` class. Attackers can execute arbitrary code and commands by crafting a malicious serialized `.mdl` payload, exploiting the use of `pickle.load()` on data from potentially untrusted sources. This vulnerability allows for remote code execution (RCE) by deceiving victims into loading a seemingly harmless checkpoint during a normal training process, thereby enabling attackers to execute arbitrary code on the targeted machine. Note that the payload file is a hidden file, making it difficult for the victim to detect tampering. More importantly, during the model training process, after the `.mdl` file is loaded and executes arbitrary code, the normal training process remains unaffected'meaning the user remains unaware of the arbitrary code execution.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2025-50472 being exploited?

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

Public exploit code:

- Technical Details and Exploit for CVE-2025-50472 (github_poc): https://github.com/Before-Rain/CVE-2025-50472

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50472 is a critical unsafe deserialization vulnerability in n/a, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50472 exists.

Affected product: n/a. 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-50472/ (Markdown: https://insights.sbomify.com/CVE-2025-50472/index.md)
```

## Sources

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

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