CVE-2025-71347
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.33 fails to detect malicious pickle files using numpy.f2py.crackfortran.param_eval function in reduce methods, allowing attackers to bypass security checks. Remote attackers can embed undetected code in pickle files that executes during deserialization, enabling arbitrary code execution in applications loading untrusted pickle data.
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.33 fails to detect malicious pickle files that use the numpy.f2py.crackfortran.param_eval function within reduce methods, allowing attackers to embed and execute arbitrary code during deserialization by bypassing the scanner's security checks.
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 installed picklescan versionRun 'pip show picklescan' or 'pip list | grep picklescan' to see the installed version numberAffected if The version listed is lower than 0.0.33 (e.g., 0.0.32, 0.0.30, etc.)
-
Confirm pickle file scanning workflowReview application code or configuration to determine if picklescan is used to scan pickle files from untrusted sourcesAffected if The application uses picklescan to validate pickle files from external or untrusted inputs
-
Verify numpy dependency usageCheck if the application environment has numpy installed and if pickle files are loaded using pickle.load(), pickle.loads(), or similar deserialization methodsAffected if The application loads pickle files and numpy is present in the environment, allowing the param_eval bypass to function
You are affected if picklescan version is below 0.0.33 AND your application uses picklescan to scan pickle files from untrusted sources that may contain the numpy.f2py.crackfortran.param_eval bypass 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.33 or later which includes detection for this bypass technique, and ensure applications loading untrusted pickle data implement defense-in-depth beyond file scanning.
0.0.33
- Upgrade picklescan to version 0.0.33 or later using your package manager (e.g., pip install picklescan>=0.0.33)
- Verify the installed version matches or exceeds 0.0.33 by running: picklescan --version
- Regenerate or re-scan any previously scanned pickle files to ensure the updated scanner properly detects malicious payloads using numpy.f2py.crackfortran.param_eval
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71347 — 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-71347 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