CVE-2025-70560
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBoltz 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBoltz 2.0.0 uses Python's pickle module to deserialize molecule data files without any validation. This insecure deserialization vulnerability allows an attacker who can place a malicious pickle file in a directory processed by boltz to achieve arbitrary code execution upon file loading.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Boltz versionRun 'pip show boltz' or check your package manager to determine the installed version of the Jwohlwend Boltz packageAffected if The installed version is exactly 2.0.0
-
Locate molecule data file loading codeSearch the Boltz installation or source code for usage of pickle.load(), pickle.loads(), or the 'pickle' module in the context of loading molecule data filesAffected if The code uses pickle to deserialize molecule data files without validation
-
Check for molecule data processing directoriesInspect the application configuration and runtime environment to identify directories where molecule data files are loaded fromAffected if Molecule data files from configurable or user-accessible directories are loaded via pickle
-
Identify file types being deserializedReview the file loading functions to determine if .pkl, .pickle, or other serialized file extensions are processed by the applicationAffected if The application loads files with .pkl or .pickle extensions as molecule data
-
Verify no input validation existsExamine the deserialization code path for any signature validation, allowlist checks, or safe deserialization alternatives before pickle is calledAffected if No validation or safe deserialization method is implemented before unpickling molecule data files
If Jwohlwend Boltz 2.0.0 is installed and the application loads molecule data files using Python's pickle module without validation, the environment is vulnerable to arbitrary code execution via malicious pickle files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace pickle with a safe serialization format (e.g., JSON, MessagePack) or implement a restricted unpickler that only allows whitelisted classes. Validate all input files before deserialization.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-70560 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data