CVE-2025-71369
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 that use torch.utils.data.datapipes.utils.decoder.basichandlers in reduce methods, allowing attackers to bypass safety checks. Remote attackers can embed undetected malicious code in pickle files that executes during deserialization, enabling remote code execution.
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 version 0.0.28 fails to detect malicious pickle files that leverage torch.utils.data.datapipes.utils.decoder.basichandlers within reduce methods, enabling attackers to embed malicious code that bypasses the scanner's safety checks and executes during deserialization.
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.
-
Check if picklescan is installedRun 'pip show picklescan' or 'pip list | grep picklescan' to see if the package is present in your Python environmentAffected if picklescan is not installed - you are not using this tool for pickle file scanning
-
Determine the installed version of picklescanRun 'pip show picklescan' and look for the Version field, or use 'pip list' to see the version numberAffected if The version is lower than 0.0.28 (e.g., 0.0.27, 0.0.26, etc.) - your scanner can be bypassed by specially crafted pickle files
-
Identify if you scan pickle files that use torch.datapipesInspect the pickle files you scan or the data pipelines that feed into your scanning process. Look for references to 'torch.utils.data.datapipes.utils.decoder' or 'basichandlers' in your input data or processing flowAffected if You scan pickle files that leverage torch.utils.data.datapipes.utils.decoder.basichandlers within reduce methods - these can bypass the vulnerable version of picklescan
You are affected if picklescan version is below 0.0.28 and you rely on it to scan pickle files potentially containing torch.datapipes.decoder 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; avoid deserializing pickle files from untrusted sources and consider using safer serialization formats like JSON or MessagePack where possible.
picklescan 0.0.28
- Identify the environment where picklescan is installed (e.g., pip, poetry, conda)
- Run 'pip install picklescan>=0.0.28' to upgrade to the fixed version
- Verify the installed version using 'pip show picklescan' or 'pip list' to confirm version 0.0.28 or later is installed
- If picklescan is used in automated scanning pipelines, update any pinned version dependencies to require 0.0.28 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71369 — 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-71369 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