CVE-2025-71349
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 the built-in trace.Trace.run function when analyzing pickle files, allowing attackers to embed undetected malicious code. Remote attackers can craft malicious pickle files using trace.Trace.run in the reduce method to achieve arbitrary code execution when pickle.load processes the file.
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 the trace.Trace.run function when scanning pickle files. Attackers can craft malicious pickle files that use trace.Trace.run in the __reduce__ method, achieving arbitrary code execution when pickle.load() deserializes the file.
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.
-
Check picklescan versionRun 'pip show picklescan' or 'pip list | grep picklescan' to see the installed versionAffected if version is below 0.0.29
-
Verify pickle scanning usageDetermine if picklescan is used to analyze pickle files from untrusted or external sourcesAffected if picklescan is used to scan untrusted pickle files and version is below 0.0.29
-
Review scanning workflowCheck if picklescan is integrated into automated pipelines or file upload processes that rely on its detection capabilitiesAffected if the scanning results influence decisions about loading pickle files and the installed version is vulnerable
You are affected if picklescan version is below 0.0.29 and you rely on it to detect malicious pickle files, as the scanner will fail to identify payloads using trace.Trace.run in 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.29 or later which adds detection for trace.Trace.run. Avoid loading untrusted pickle files and prefer safer serialization formats like JSON.
picklescan >= 0.0.29
- 1. Identify the current version of picklescan installed in your environment using: pip show picklescan or pip list | grep picklescan
- 2. Upgrade picklescan to version 0.0.29 or later using: pip install --upgrade picklescan>=0.0.29
- 3. Verify the upgrade was successful by running: pip show picklescan and confirming the version number
- 4. Re-scan any previously analyzed pickle files to ensure they are now properly detected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71349 — 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-71349 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