AIKIDO-2026-333968
pylint is vulnerable to Insecure Deserialization
54
Medium Risk
This Affects:
pylintTL;DR
Pylint's result cache in PYLINT_HOME is stored as a pickle file and reloaded with pickle.load on the next run. Anyone who can write to that cache directory, such as another user on a shared or group writable host, can plant a crafted pickle that executes arbitrary code when pylint next loads its stats. The fix stores the cache as JSON instead and regenerates any invalid or legacy cache rather than deserializing it.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you run pylint against a PYLINT_HOME cache directory that is shared with or writable by other untrusted users on the same host.
Background info
pylint is vulnerable to Insecure Deserialization in versions 0.0.1 - 4.0.8.
How to fix this
Upgrade the pylint library to the patch version.
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.