CVE-2025-71355
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.25 fails to detect unsafe global functions in the Numpy library, allowing attackers to bypass static analysis and execute arbitrary code during deserialization. Attackers can craft malicious pickle files using numpy.testing._private.utils.runstring within the reduce method to import dangerous libraries like os and execute arbitrary OS commands when the pickle file is loaded.
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.25 fails to detect the unsafe numpy.testing._private.utils.runstring function when used within pickle reduce methods, allowing attackers to craft malicious pickle files that bypass static analysis and execute arbitrary OS commands during deserialization by importing dangerous libraries like os.
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
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 display the installed version numberAffected if The version listed is 0.0.24 or earlier (versions prior to 0.0.25 lack the detection rule for this bypass)
-
Confirm pickle scanning workflowIdentify whether your application or security pipeline uses Picklescan to analyze pickle files from external or untrusted sourcesAffected if Picklescan is actively used to scan pickle files but the version is vulnerable to the bypass
-
Check for numpy imports in scanned payloadsIf possible, examine a sample pickle file scanned by Picklescan or review scan logs for entries involving numpy or the runstring functionAffected if Picklescan reports the pickle as safe despite containing numpy.testing._private.utils.runstring in a reduce method (indicating the bypass was not detected)
You are affected if your installed Picklescan version is 0.0.24 or earlier and you rely on it to detect malicious pickle files that exploit the numpy.testing._private.utils.runstring technique to bypass static analysis.
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.25 or later to include detection for this bypass technique. Additionally, never load pickle files from untrusted sources and consider using safer serialization formats like JSON where possible.
Picklescan version 0.0.25 or later
- Check the current installed version of picklescan by running: pip show picklescan or pip list | grep picklescan
- Upgrade picklescan to version 0.0.25 or later by running: pip install picklescan>=0.0.25
- Verify the upgrade was successful by running: pip show picklescan and confirming the version is 0.0.25 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71355 — 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-71355 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