The vulnerability in picklescan prior to version 0.0.34 involves a failure to detect _operator.attrgetter function calls embedded within pickle payloads. Attackers can exploit this by creating malicious pickle files that leverage _operator.attrgetter in reduce methods, enabling arbitrary code execution when the pickle.load() function processes these files. This represents a code injection risk through unsafe deserialization, categorized under CWE-502.

Successful exploitation allows remote attackers to execute arbitrary code on systems that deserialize malicious pickle files using vulnerable picklescan versions. This can lead to full system compromise depending on the privileges of the process performing the deserialization.

No patch or official fix is currently confirmed or available. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is released, avoid loading pickle files from untrusted sources or implement additional validation controls to detect malicious payloads.