dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-71374

HIGH · 8.1 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

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 · unedited
picklescan before 0.0.29 fails to detect the built-in python profile.Profile.run function when used in pickle reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files that bypass picklescan detection and achieve code execution upon 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 confidence

picklescan before 0.0.29 fails to detect the built-in python profile.Profile.run function when used in pickle __reduce__ methods, allowing attackers to craft malicious pickle files that bypass detection and achieve arbitrary code execution upon deserialization.

MitigationUpgrade picklescan to version 0.0.29 or later which includes detection for the profile.Profile.run evasion technique. Alternatively, disable pickle deserialization entirely or use safer serialization formats like JSON.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if picklescan is installed
    Run 'pip show picklescan' or check your requirements.txt / lock file for the picklescan package
    Affected if picklescan is present in the environment and used for scanning pickle files
  2. Determine the installed version of picklescan
    Run 'pip show picklescan' and note the Version field, or run 'pip list | grep picklescan'
    Affected if The version is lower than 0.0.29 (e.g., 0.0.28, 0.0.27, etc.)
  3. Check if your code uses pickle.load or pickle.loads on untrusted input
    Search codebase for patterns like 'pickle.load(', 'pickle.loads(', 'unpickle', or usage of the pickle module with external data sources
    Affected if Your application deserializes pickle data from untrusted sources without additional validation
  4. Verify picklescan is used as a detection layer before pickle deserialization
    Search for picklescan.scan, picklescan.scandata, or similar function calls in your code that validate pickle data before calling pickle.load
    Affected if picklescan is used to scan pickle files but the version is below 0.0.29
  5. Check for profile.Profile usage in pickled data
    If you have sample pickle files, inspect them for references to 'profile.Profile' or 'profile' module in the serialized data, or test with picklescan version 0.0.29+ to see if detection improves
    Affected if picklescan version is below 0.0.29 and you process pickle files from untrusted sources

You are affected if picklescan with version below 0.0.29 is installed and used to scan pickle files from untrusted sources, as the profile.Profile.run evasion technique would bypass detection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade picklescan to version 0.0.29 or later which includes detection for the profile.Profile.run evasion technique. Alternatively, disable pickle deserialization entirely or use safer serialization formats like JSON.

Recommended fix High confidence

picklescan 0.0.29

  1. Check the currently installed version of picklescan using: pip show picklescan or pip freeze | grep picklescan
  2. Upgrade picklescan to version 0.0.29 or later using: pip install picklescan>=0.0.29
  3. Verify the upgrade was successful by running: pip show picklescan and confirming the version is 0.0.29 or higher
  4. If picklescan is used in automated scanning pipelines, ensure the scanning tool picks up the new version by restarting any relevant services

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-71374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-71374 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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