Picklescan versions prior to 0.0.33 fail to detect malicious pickle files that exploit the numpy.f2py.crackfortran._eval_length function during unpickling. This allows attackers to execute arbitrary Python code when a crafted pickle is loaded, despite Picklescan reporting the file as safe. The vulnerability enables arbitrary code execution in workflows relying on Picklescan to vet untrusted pickle or PyTorch artifacts, potentially facilitating supply-chain poisoning of shared model files.