The root cause of this vulnerability is an incomplete blocklist in picklescan. The scanner was configured to block profile.Profile.run and profile.Profile.runctx but failed to block the module-level functions profile.run and profile.runctx. Both of these module-level functions can execute arbitrary code via exec(). An attacker could craft a malicious pickle file that calls profile.run('...arbitrary code...'). When this pickle is loaded in an application that uses picklescan for security, picklescan would fail to detect the dangerous call, allowing the arbitrary code to be executed. The patch resolves this by blocking all functions from the profile module ("profile": "*"), ensuring that profile.run and profile.runctx are no longer allowed.