CVE-2025-71369: picklescan - Unsafe Deserialization via torch.utils.data.datapipes.utils.decoder.basichandlers
picklescan before 0.0.28 fails to detect malicious pickle files that use torch.utils.data.datapipes.utils.decoder.basichandlers in reduce methods, allowing attackers to bypass safety checks. Remote attackers can embed undetected malicious code in pickle files that executes during deserialization, enabling remote code execution.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
picklescanto a version that resolves this vulnerability.Fixed in 0.0.28 - Compensating control
Ensure picklescan is used for pickle-file validation so files are rejected if they contain unsafe deserialization payloads; versions before 0.0.28 may fail to detect payloads that use torch.utils.data.datapipes.utils.decoder.basichandlers in reduce methods.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-71369?
The severity of CVE-2025-71369 is rated as high with a score of 8.1.
How does CVE-2025-71369 affect picklescan?
CVE-2025-71369 allows remote attackers to embed malicious code in pickle files that can execute during deserialization.
How do I fix CVE-2025-71369?
To fix CVE-2025-71369, upgrade picklescan to version 0.0.28 or later to mitigate unsafe deserialization risks.
Who is affected by CVE-2025-71369?
Users of picklescan versions prior to 0.0.28 are affected by CVE-2025-71369 due to unsafe deserialization practices.
What is the impact of CVE-2025-71369 on data security?
CVE-2025-71369 poses a significant threat to data security by allowing attackers to bypass safety checks and execute harmful code.