dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-71363

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.30 fails to detect cProfile.run function calls in pickle reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files with cProfile.run payloads 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.30 has a detection bypass where cProfile.run function calls embedded in pickle __reduce__ methods are not identified as malicious. Attackers can craft pickle files containing cProfile.run payloads that execute arbitrary code upon deserialization, bypassing the scanner entirely.

MitigationUpgrade picklescan to version 0.0.30 or later to include cProfile.run detection. Do not rely solely on picklescan for pickle file security; implement additional safeguards such as restricted unpicklers, input validation, and network isolation for pickle deserialization endpoints.

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. Check if picklescan is installed
    Run `pip show picklescan` or `pip list | grep picklescan` to see if the package is present in your Python environment
    Affected if picklescan is installed and you use it to scan pickle files from untrusted sources
  2. Determine the installed version of picklescan
    Run `pip show picklescan` and look for the Version field, or use `pip list` to see the version number
    Affected if The version shown is lower than 0.0.30 (for example, 0.0.29, 0.0.28, etc.)
  3. Verify your pickle deserialization workflow
    Inspect any scripts or code that use picklescan to scan pickle files before loading them, looking for calls to picklescan functions or CLI commands scanning untrusted pickle files
    Affected if You rely on picklescan to validate pickle files from untrusted or external sources before deserialization

You are affected if picklescan is installed with a version before 0.0.30 and you depend on it to detect malicious pickle payloads from untrusted sources.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade picklescan to version 0.0.30 or later to include cProfile.run detection. Do not rely solely on picklescan for pickle file security; implement additional safeguards such as restricted unpicklers, input validation, and network isolation for pickle deserialization endpoints.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-71363 — 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-71363 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