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

> Attackers can execute arbitrary code by supplying crafted data to the ModelCache for LLM library due to a deserialization vulnerability.

- **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:** 11 Aug 2025
- **Updated:** 11 Aug 2025
- **Also known as:** GHSA-2rhh-j8hg-6qg4

## What is CVE-2025-45146?

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

### Official description

ModelCache for LLM through v0.2.0 was discovered to contain an deserialization vulnerability via the component /manager/data_manager.py. This vulnerability allows attackers to execute arbitrary code via supplying crafted data.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Codefuse Modelcache.

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

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

## Is CVE-2025-45146 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45146 is a critical unsafe deserialization vulnerability in n/a, published on 11 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-45146 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-45146/ (Markdown: https://insights.sbomify.com/CVE-2025-45146/index.md)
```

## Sources

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

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