Advisory

GHSA-22qq-2fwx-7p67

Also known as: CVE-2026-114608

Summary

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

Details

Impact

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 upgrading do not point PYLINT_HOME to an untrusted, shared, or group-writable directory. The default value, ~/.cache/pylint, is writable only by the user running pylint.

Credits

  • Reported privately via Tidelift coordinated disclosure (Dan Lenz).

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-10-27 14:46 UTC
Modified
2026-10-27 15:00 UTC

Affected packages and fixes

pylint

PyPI · All systems

Affected

  • introduced 0, fixed 4.0.9 (ecosystem)

Fixed versions

4.0.9

Fix

  • Fixed version 4.0.9
    pip install --upgrade pylint==4.0.9

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences