GitHub Advisoryadvisory · PyPI

GHSA-6vqj-c2q5-j97w Picklescan has a missing detection when calling built-in python profile.Profile.runctx

HIGH Published 2025-08-26 Modified 2026-09-23 Official page ↗
Aliases
CVE-2025-71341
Ecosystem
PyPI
Packages
picklescan
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Weaknesses
CWE-502
Reviewed
2025-08-26

Affected packages

• PyPI picklescan: < 0.0.29 → fixed in 0.0.29

Description

Summary Using profile.Profile.runctx, which is a built-in python library function to execute remote pickle file. Details The attack payload executes in the following steps: First, the attacker craft the payload by calling to profile.Profile.runctx 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. PoC ``` class EvilProfileRunctx: def __reduce__(self): from profile import Profile payload = "__import__('os').system('whoami')" return Profile.runctx, (Profile(), payload, {}, {}) ``` 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. Corresponding https://github.com/FredericDT https://github.com/Qhaoduoyu

Related

Alias · CVE (1)

  • CVE-2025-71341 picklescan before 0.0.29 fails to detect the profile.Profile.runctx function when analyzing pickle files, allowing attackers to embed… vulnerability

Weakness · CWE (1)

  • CWE-502 Deserialization of Untrusted Data weakness

References