CVE-2025-71362
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 unsafe deserialization when numpy.f2py.crackfortran functions call eval on arbitrary strings. Attackers can embed malicious code in pickle files that executes when loaded from untrusted sources.
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 unsafe deserialization attacks leveraging numpy.f2py.crackfortran functions, which internally call eval() on attacker-controlled strings embedded in malicious pickle files. When loaded from untrusted sources, these crafted pickle files can execute arbitrary code despite picklescan's scanning.
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 check your package manager to retrieve the installed version numberAffected if The installed version is below 0.0.33 (or the version cannot be determined, indicating an old or unversioned installation)
-
Verify numpy presenceRun 'pip show numpy' or check your dependencies to confirm numpy is installed in the environment where picklescan runsAffected if numpy is installed, as the vulnerability specifically exploits numpy.f2py.crackfortran functions that contain eval() calls
-
Confirm pickle file scanning workflowReview your application's code or pipeline to determine if picklescan is actively used to scan pickle files loaded from external or untrusted sourcesAffected if Picklescan is used to scan pickle files originating from untrusted or external sources before loading them
-
Check for unsafe pickle loading patternsSearch your codebase for pickle.load(), pickle.loads(), or similar unpickling functions that handle data from untrusted input, and verify if picklescan is invoked on such inputsAffected if Your system loads pickle files from untrusted sources without first passing them through picklescan, or picklescan is invoked but uses a version vulnerable to this bypass
You are affected if picklescan version is below 0.0.33 AND your system uses picklescan to scan pickle files from untrusted sources that could contain malicious numpy.f2py.crackfortran 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.33 or later to obtain detection for numpy.f2py.crackfortran eval() exploitation. Additionally, avoid loading pickle files from untrusted sources regardless of scanner results.
picklescan 0.0.33
- Check the current installed version of picklescan by running: pip show picklescan or pip list | grep picklescan
- Upgrade picklescan to version 0.0.33 or later by running: pip install picklescan>=0.0.33
- Verify the upgrade was successful by running: pip show picklescan and confirming the version is 0.0.33 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71362 — 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-71362 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