# CVE-2025-70560: Boltz contains an insecure deserialization vulnerability in its molecule loading functionality

> An attacker can achieve arbitrary code execution by placing a malicious pickle file in a directory processed by the Boltz library.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 19 Feb 2026
- **Also known as:** GHSA-fjm6-8xp2-4fwc, PYSEC-2026-1224

## What is CVE-2025-70560?

CVE-2025-70560 is a high-severity unsafe deserialization vulnerability in n/a, published on 3 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Boltz 2.0.0 contains an insecure deserialization vulnerability in its molecule loading functionality. The application uses Python pickle to deserialize molecule data files without validation. An attacker with the ability to place a malicious pickle file in a directory processed by boltz can achieve arbitrary code execution when the file is loaded.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

3 open source packages ship an affected version, including boltz. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `boltz` | PyPI | All versions to 2.0.0 | None |
| `boltz` | PyPI | All versions to 2.0.0 | None |
| `boltz` | PyPI | All versions to 2.0.0 | None |

Products: Jwohlwend Boltz.

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

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

## Is CVE-2025-70560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70560 is a high-severity unsafe deserialization vulnerability in n/a, published on 3 Feb 2026. 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-70560 in the wild and no public exploit code.

Affected packages and fixed versions:
- boltz (PyPI): affected all versions up to 2.0.0; no fix listed
- boltz (PyPI): affected all versions up to 2.0.0; no fix listed
- boltz (PyPI): affected all versions up to 2.0.0; 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-70560/ (Markdown: https://insights.sbomify.com/CVE-2025-70560/index.md)
```

## Sources

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

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