# CVE-2025-5148: FunAudioLLM InspireMusic Pickle Data model.py load_state_dict deserialization

> Local attackers can execute arbitrary code via unsafe pickle deserialization in the model loading function of FunAudioLLM InspireMusic.

- **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:** 25 May 2025
- **Updated:** 28 May 2025
- **Also known as:** GHSA-pgp9-g5q8-j3wp, PYSEC-2026-1464

## What is CVE-2025-5148?

CVE-2025-5148 is a medium-severity unsafe deserialization vulnerability in FunAudioLLM InspireMusic, published on 25 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in FunAudioLLM InspireMusic up to bf32364bcb0d136497ca69f9db622e9216b029dd. It has been classified as critical. Affected is the function load_state_dict of the file inspiremusic/cli/model.py of the component Pickle Data Handler. The manipulation leads to deserialization. An attack has to be approached locally. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The name of the patch is 784cbf8dde2cf1456ff808aeba23177e1810e7a9. It is recommended to apply a patch to fix this issue.

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

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

3 open source packages ship an affected version, including inspiremusic.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `inspiremusic` | PyPI | All versions to 0.0.1.dev0 | None |
| `inspiremusic` | PyPI | All versions to 0.0.1.dev0 | None |
| `inspiremusic` | PyPI | All versions to 0.0.1.dev0 | None |

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

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

## Is CVE-2025-5148 being exploited?

There is no known exploitation of CVE-2025-5148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5148 is a medium-severity unsafe deserialization vulnerability in FunAudioLLM InspireMusic, published on 25 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5148 in the wild and no public exploit code.

Affected packages and fixed versions:
- inspiremusic (PyPI): affected all versions up to 0.0.1.dev0; no fix listed
- inspiremusic (PyPI): affected all versions up to 0.0.1.dev0; no fix listed
- inspiremusic (PyPI): affected all versions up to 0.0.1.dev0; no fix listed

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-5148/ (Markdown: https://insights.sbomify.com/CVE-2025-5148/index.md)
```

## Sources

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

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