PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-71350 picklescan CVE debrief

CVE-2025-71350 is a high-severity vulnerability in picklescan before version 0.0.28. The vulnerability allows attackers to embed undetected code in pickle files that executes remote commands when loaded by victims. This issue arises from the failure to detect malicious pickle files using the torch.utils.collect_env.run function in reduce methods. Affected product deployments should be identified in managed environments, and owners should be assigned for follow-up. The official advisory or CVE record should be reviewed to validate affected scope, severity, and vendor guidance. For exposed systems, compensating controls should be reviewed while remediation is scheduled and verified.

Vendor
picklescan
Product
Unknown
CVSS
HIGH 7.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-30
Original CVE updated
2026-10-05
Advisory published
2026-06-30
Advisory updated
2026-10-05

Who should care

Defenders responsible for systems using picklescan should assess exposure and prioritize verification and remediation efforts. This includes verifying the version of picklescan in use, upgrading to version 0.0.28 or later, and implementing compensating controls to detect and prevent the loading of malicious pickle files.

Why it matters

CVE-2025-71350 is a high-severity vulnerability in picklescan that allows remote code execution when loading malicious pickle files. Defenders should prioritize verification and remediation efforts to prevent exploitation.

  • Remote code execution is possible when loading malicious pickle files
  • Defenders must verify the version of picklescan in use and upgrade to version 0.0.28 or later
  • Exposure assessment and compensating controls are necessary to prevent exploitation

Technical summary

The vulnerability in picklescan before version 0.0.28 allows attackers to embed undetected code in pickle files that executes remote commands when loaded by victims. This issue arises from the failure to detect malicious pickle files using the torch.utils.collect_env.run function in reduce methods.

Defensive priority

Defenders should prioritize verifying the version of picklescan in use and upgrading to version 0.0.28 or later. Additionally, defenders should assess exposure and implement compensating controls to detect and prevent the loading of malicious pickle files.

Recommended defensive actions

  • Verify the version of picklescan in use and upgrade to version 0.0.28 or later
  • Assess exposure and implement compensating controls to detect and prevent the loading of malicious pickle files
  • Monitor systems for suspicious activity related to pickle file loading

Evidence notes

The CVE record and NVD entry provide information on the vulnerability, but details on exploitation, impact, and remediation are limited. Further verification is required to determine the full scope of affected systems and to confirm the effectiveness of the proposed fix.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-71350 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-71350

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-71350 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-71350

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.