The vulnerability in picklescan allows an attacker to execute arbitrary code on the host. It arises from unsafe deserialization of pickle files and uses obfuscated eval calls that are hidden inside callable objects accessed via getattr. The flaw is classified as CWE‑502 and enables attackers to embed malicious code that bypasses simple detection mechanisms and runs when the pickle is loaded from an untrusted source. If exploited, the attacker gains complete control of the affected system, compromising confidentiality, integrity, and availability.

Picklescan versions prior to 1.0.1 are affected. The product name is picklescan, and any deployment that loads pickle data supplied by external actors is at risk.

The CVSS score of 9.3 indicates a critical severity. The EPSS score is <1%, suggesting that, while the exploit exists, it has low likelihood of being discovered in the wild at present, and the vulnerability is not yet listed in the CISA KEV catalog. The likely attack path involves an unauthenticated actor creating a malicious pickle file, delivering it to a vulnerable application, and triggering the load function. Because the attack does not require special privileges, any user or process capable of executing picklescan can be leveraged for exploitation.