CVE-2025-71350
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 · uneditedpicklescan before 0.0.28 fails to detect malicious pickle files using torch.utils.collect_env.run function in reduce methods. Attackers can embed undetected code in pickle files that executes remote commands when loaded by victims.
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 confidencepicklescan before 0.0.28 fails to detect malicious pickle files that use torch.utils.collect_env.run function within reduce methods. Attackers can embed code that executes remote commands when victims load these crafted pickle files, bypassing the scanner's detection capabilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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 picklescan installationRun 'pip show picklescan' or 'pip list | grep picklescan' to find the installed versionAffected if Version displayed is lower than 0.0.28 or the package is not found
-
Check picklescan version numberExtract the version from the pip output and compare it to 0.0.28Affected if The version string shows a number lower than 0.0.28 (for example, 0.0.27, 0.0.26, etc.)
-
Verify pickle file scanning workflowInspect how picklescan is invoked in your environment - check CI/CD pipelines, scripts, or automation that call picklescan against pickle filesAffected if Picklescan is used to scan pickle files from potentially untrusted sources and the tool version is below 0.0.28
-
Confirm torch pickle handlingReview whether your picklescan scans pickle files that may contain PyTorch-related data using torch.utils.collect_env.run in reduce methodsAffected if You scan PyTorch pickle files and rely on picklescan for security filtering with a version before 0.0.28
You are affected if picklescan version is below 0.0.28 and you use it to scan pickle files, particularly PyTorch-related ones that could contain malicious torch.utils.collect_env.run payloads.
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.
dbcve · scopedUpgrade picklescan to version 0.0.28 or later to address the detection gap. Additionally, avoid loading pickle files from untrusted sources and consider safer serialization formats like JSON where possible.
picklescan version 0.0.28 or later
- Verify current picklescan version using: pip show picklescan or pip list | grep picklescan
- Upgrade picklescan to version 0.0.28 or later using: pip install picklescan>=0.0.28
- Verify the upgrade was successful by checking the installed version
- If using picklescan in automated scanning workflows, verify the scanner correctly identifies malicious pickle files with torch.utils.collect_env.run in reduce methods
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71350 — 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-71350 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