CVE-2025-71359
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.29 fails to detect malicious pickle payloads that utilize lib2to3.pgen2.grammar.Grammar.loads in the reduce method, allowing remote code execution. Attackers can craft pickle files embedding dangerous code that evades picklescan detection and executes during pickle.load() deserialization.
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.29 fails to detect malicious pickle payloads that abuse lib2to3.pgen2.grammar.Grammar.loads within the __reduce__ method, enabling attackers to craft evasive pickle files that bypass scanner detection and achieve remote code execution upon pickle.load() 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.
-
Verify picklescan is installedRun 'pip show picklescan' or check your dependency list for the picklescan packageAffected if picklescan is not installed in your environment - you are not affected as a scanner user, but also not protected
-
Check the installed version of picklescanRun 'pip show picklescan' and look for the Version field, or run 'pip index versions picklescan' to see available versionsAffected if The installed version is lower than 0.0.29 (e.g., 0.0.28, 0.0.27, etc.) - you are running a vulnerable version
-
Identify pickle files scanned from untrusted sourcesReview your picklescan usage logs or scripts that invoke picklescan on pickle files from external/untrusted sourcesAffected if You scan pickle files from untrusted or user-controlled sources - these could contain Grammar.loads evasion payloads that your version of picklescan would miss
-
Test for Grammar.loads detection capabilityCreate a test pickle file using lib2to3.pgen2.grammar.Grammar.loads within __reduce__ and scan it with your installed picklescan version to see if it gets flaggedAffected if Your picklescan version does not detect this specific evasion technique - the malicious payload would be allowed through undetected
You are affected if you have picklescan installed with a version below 0.0.29 AND you use it to scan pickle files from untrusted sources that could contain the Grammar.loads evasion technique.
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.29 or later to include detection for Grammar.loads-based payloads; avoid loading untrusted pickle files regardless of scanner results.
0.0.29
- Upgrade picklescan to version 0.0.29 or later using your package manager (e.g., pip install picklescan==0.0.29)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71359 — 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-71359 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