# CVE-2026-31232: Deserialization in n/a

> Attackers can achieve remote code execution by tricking users into loading malicious model files due to insecure deserialization in CosyVoice.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-chxf-r8w4-qgr9

## What is CVE-2026-31232?

CVE-2026-31232 is a high-severity unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The CosyVoice project thru commit 6e01309e01bc93bbeb83bdd996b1182a81aaf11e (2025-30-21) contains an insecure deserialization vulnerability (CWE-502) in its model loading process. When loading model files (.pt) from a user-specified directory (via the --model_dir argument), the code uses torch.load() without the security-restrictive weights_only=True parameter. This allows the deserialization of arbitrary Python objects via the Pickle module. An attacker can exploit this by providing a maliciously crafted model directory containing .pt files with embedded pickle payloads. When a victim loads this directory using CosyVoice's web interface, the malicious payload is executed, leading to remote code execution on the victim's system.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-31232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31232 is a high-severity unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-31232 in the wild and no public exploit code.

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

## Sources

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

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