CVE-2025-71366
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 torch.utils.bottleneck.__main__.run_cprofile function calls in pickle files, allowing attackers to bypass safety checks. Remote attackers can embed undetected code in pickle files to achieve arbitrary code execution when victims load the files.
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 torch.utils.bottleneck.__main__.run_cprofile function calls embedded in pickle files, allowing attackers to bypass the scanner's safety checks and achieve arbitrary code execution when victims load the crafted files.
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 picklescan installed versionRun `pip show picklescan` or `pip list | grep picklescan` to see the installed version numberAffected if The version displayed is earlier than 0.0.28 (e.g., 0.0.27, 0.0.26, etc.)
-
Verify picklescan is used in your workflowInspect any scripts, CI pipelines, or automation that invoke picklescan to scan pickle filesAffected if You use picklescan to validate pickle files from untrusted or external sources before loading them
-
Confirm pickle file loading from external sourcesSearch your codebase for `pickle.load`, `pickle.loads`, `torch.load`, or similar pickle deserialization calls that process files from users, uploads, or network sourcesAffected if Your application loads pickle files from untrusted sources and relies on picklescan as a safety check before loading
-
Check for torch installationRun `pip show torch` to see if the PyTorch library is installed in the environmentAffected if torch is installed in the same environment where pickle files are loaded, enabling the bypass vector to execute code
You are affected if picklescan version is below 0.0.28 AND you rely on it to scan pickle files from untrusted sources that could contain the torch.utils.bottleneck.__main__.run_cprofile payload.
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 include detection for this bypass vector; avoid loading untrusted pickle files regardless of scan results as a defense-in-depth measure.
0.0.28
- Upgrade picklescan to version 0.0.28 or later using pip: pip install picklescan>=0.0.28
- Verify the upgrade was successful by checking the installed version: pip show picklescan
- Ensure your application uses the updated version for scanning pickle files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71366 — 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-71366 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