dbcve.org
CWE-693Weakness · CWE-693

CVE-2025-71373

HIGH · 8.1 CVSS v3.1 Published 2026-07-04
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 7 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.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle payloads using operator.methodcaller that execute arbitrary code when loaded, compromising systems relying on picklescan for validation.

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 version 0.0.33 fails to detect operator.methodcaller function calls embedded in pickle files, enabling attackers to craft malicious payloads that bypass the security scanner's validation checks. When such crafted pickle files are deserialized, they can execute arbitrary code on the target system.

MitigationUpgrade picklescan to version 0.0.33 or later to patch the detection bypass. Additionally, enforce a defense-in-depth strategy by never loading pickle files from untrusted or unauthenticated sources, regardless of scanner results.

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 not installed at all (the scanner is not in use)
  2. Verify picklescan version
    Run 'pip show picklescan' and look for the Version field, or run 'pip index versions picklescan' to compare against version 0.0.33
    Affected if The installed version is lower than 0.0.33 (e.g., 0.0.32, 0.0.30, etc.)
  3. Identify picklescan usage in your code or pipeline
    Search your codebase for imports of picklescan and its scanner functions (e.g., 'from picklescan import scanner' or 'picklescan.scanner.scan_file'), or check CI/CD pipelines that invoke picklescan
    Affected if picklescan is being used as a validation step before loading pickle files
  4. Assess pickle file processing from external sources
    Review application code that loads pickle files and identify whether picklescan is called as a security check before unpickling data from untrusted or unauthenticated sources
    Affected if picklescan is used as a security gate for pickle files from untrusted sources and the installed version is below 0.0.33

You are affected if picklescan is installed, version is below 0.0.33, and it is used as a validation checkpoint for pickle files from untrusted sources since the scanner can be bypassed with operator.methodcaller payloads.

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.33 or later to patch the detection bypass. Additionally, enforce a defense-in-depth strategy by never loading pickle files from untrusted or unauthenticated sources, regardless of scanner results.

Recommended fix Moderate confidence

0.0.33 or later

  1. Identify the current version of picklescan installed in your environment (e.g., pip show picklescan or check requirements.txt)
  2. Upgrade picklescan to version 0.0.33 or later using: pip install picklescan>=0.0.33
  3. Verify the upgrade was successful by running: pip show picklescan
  4. If picklescan is used in automated validation pipelines, re-run your security scans to confirm the operator.methodcaller detection is now working

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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