Deserialization of Untrusted Data Affecting pylint package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-PYLINT-21664584
- published24 Oct 2026
- disclosed22 Oct 2026
Introduced: 22 Oct 2026
NewCVE-2026-114608 (opens in a new tab)How to fix?
There is no fixed version for Debian:unstable pylint.
NVD Description
Note: Versions mentioned in the description apply only to the upstream pylint package and not the pylint package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
Pylint is a static code analyser for Python. From 0.15.2 until 4.0.9, Pylint stores module statistics in predictable files under PYLINT_HOME and loads those files with pickle.load on a later run. An attacker who can write to a shared, group-writable, or otherwise untrusted cache directory can replace a stats cache with crafted serialized data, causing arbitrary code to execute with the privileges of the user who next runs Pylint. The default per-user cache is not normally writable by another user. This issue is fixed in version 4.0.9.
References
- https://security-tracker.debian.org/tracker/CVE-2026-114608
- https://github.com/pylint-dev/pylint/commit/58c87cffca9de2b3e89aa07b89686cbc90cfea2d
- https://github.com/pylint-dev/pylint/commit/5b241f66318220e9ba7b21ca631fbfe8e77682ca
- https://github.com/pylint-dev/pylint/releases/tag/v4.0.9
- https://github.com/pylint-dev/pylint/security/advisories/GHSA-22qq-2fwx-7p67