CVE-2025-71340
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 through 0.0.26 fails to detect malicious pickle files that invoke idlelib.pyshell.ModifiedInterpreter.runcode in __reduce__ methods. Attackers can embed undetected code in pickle files that executes arbitrary commands when the file is loaded via pickle.load(), enabling supply chain attacks on PyTorch models and saved Python objects. This is fixed in version 0.0.30.
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 versions up to 0.0.26 fail to detect malicious pickle files that abuse idlelib.pyshell.ModifiedInterpreter.runcode within __reduce__ methods. Attackers can craft pickled objects that execute arbitrary commands upon pickle.load(), enabling supply chain compromises via untrusted PyTorch models or Python object saves. The vulnerability is fixed in version 0.0.30.
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 versionRun `pip show picklescan` or `pip list | grep picklescan` to retrieve the installed version numberAffected if The installed version is 0.0.26 or lower, or any version below 0.0.30 (the scanner lacks the fix for this detection gap)
-
Confirm scan capability for ModifiedInterpreterSince the vulnerability is that the scanner fails to detect idlelib.pyshell.ModifiedInterpreter.runcode abuse in __reduce__ methods, you would need to test with a sample malicious pickle file leveraging this technique - however, this requires access to such a test file which is not providedAffected if Running a vulnerable version means the scanner may produce false negatives for pickles using the idlelib.pyshell.ModifiedInterpreter vector
You are affected if your installed picklescan version is 0.0.26 or lower (any version below 0.0.30), as the scanner will fail to detect pickle files that abuse idlelib.pyshell.ModifiedInterpreter.runcode within __reduce__ methods.
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.30 or later. Additionally, avoid loading pickle files from untrusted sources and consider using safer serialization formats like JSON or protobuf where possible.
picklescan version 0.0.30
- Verify current picklescan version by running: pip show picklescan or pip list | grep picklescan
- Upgrade to version 0.0.30 or later using: pip install picklescan>=0.0.30
- Confirm the upgrade was successful by running: pip show picklescan and verifying the version number
- If using picklescan in automated pipelines, update any pinned version constraints to require picklescan>=0.0.30
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71340 — 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-71340 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