picklescan PyPI Package Unsafe Deserialization Vulnerability Confirmed
The picklescan Python package before version 1.0.1 contains a confirmed unsafe deserialization vulnerability that allows unauthenticated users to execute arbitrary code. Users of picklescan versions prior to 1.0.1 are affected.
What happened
The picklescan package before version 1.0.1 has an unsafe deserialization vulnerability tracked as GHSA-7WX9-6375-F5WH, GHSA-82FG-2R99-H7V6, GHSA-9M3X-QQW2-H32H, GHSA-J6C9-QVP8-699F, and GHSA-VVPJ-8CMC-GX39. This vulnerability allows unauthenticated users to execute arbitrary code by hiding eval calls nested under callable objects via getattr. Attackers can embed malicious code in pickle files that evades detection but executes when the pickle is loaded from untrusted sources.
To assess your exposure, check if your software or dependencies use picklescan versions before 1.0.1. If so, you are vulnerable to this unsafe deserialization attack. The recommended action is to upgrade to picklescan version 1.0.1 or later to mitigate the vulnerability. For more details, consult the primary sources listed in the threat data.
How 0Day mitigates this
picklescan is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.