← Back to results
Vulnerability record · public intelligence
CVE-2025-71368
HIGH

Picklescan is missing detection when calling built-in python doctest.debug_script

Published Jun 30, 2026 · Updated Nov 3, 2026

Severity · CVSSHIGH · Not scored
Known exploitationNot listed
EPSS / likelihood0.84%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

Picklescan is missing detection when calling built-in python doctest.debug_script

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Using doctest.debugscript function, which is a built-in python library function to execute remote pickle file.

Potential impact

Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects.

Technical context

The attack payload executes in the following steps: First, the attacker craft the payload by calling to doctest.debugscript function in reduce method Then when the victim after checking whether the pickle file is safe by using Picklescan library and this library doesn't dectect any dangerous functions, decide to pickle.load() this malicious pickle file, thus lead to remote code execution.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. VulnCheck Advisory: picklescan - Arbitrary Code Execution via Undetected doctest.debug_script ↗

Record history

Published Jun 30, 2026 · Last refreshed Nov 3, 2026