Pylint: Arbitrary code execution via pickle deserialization of the stats cache in PYLINT_HOME

影響: pip:pylint < 4.0.9 → 4.0.9

Since 2006 / pylint 0.15.2, pylint caches its stats as pickles in PYLINT_HOME and reload them on the next run with pickle.load. Someone without access to the configuration or linted code, but with access to the cache directory (predictable PYLINT_HOME on a multi-user host) can write a crafted pickle that will runs arbitrary code when pylint access its stat cache. Patches From pylint 4.0.9, the result cache is now stored as JSON instead of pickle, preventing code-execution. Workarounds Until upg…

Read on GitHub Advisory Database

On 10/27/2026, 11:46 PM, GitHub Advisory Database published "Pylint: Arbitrary code execution via pickle deserialization of the stats cache in PYLINT_HOME" (type: Advisory). Severity is "Medium" (medium). Related technologies: Python. CVE: CVE-2026-114608.