Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Pylint versions before 4.0.9 are vulnerable because they store cached stats as Python pickles in PYLINT_HOME and load them with pickle.load on later runs. An attacker who can write to the cache directory, such as a predictable PYLINT_HOME on a shared multi-user host, could plant a crafted pickle and run arbitrary code when pylint reads it. Upgrade to pylint 4.0.9 or later, which stores the cache as JSON, and until then avoid pointing PYLINT_HOME at untrusted, shared, or group-writable directories.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.4 | Medium | 4.0 | CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0011, the 1st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:07 UTC First seen by agentprime
- 31 Oct 2026, 14:07 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-22qq-2fwx-7p67
- OSV: GHSA-22qq-2fwx-7p67
- github.com/pylint-dev/pylint/security/advisories/GHSA-22qq-2fwx-7p67
- nvd.nist.gov/vuln/detail/CVE-2026-114608
- github.com/pylint-dev/pylint/commit/58c87cffca9de2b3e89aa07b89686cbc90cfea2d
- github.com/pylint-dev/pylint/commit/5b241f66318220e9ba7b21ca631fbfe8e77682ca
- github.com/pylint-dev/pylint
- github.com/pylint-dev/pylint/releases/tag/v4.0.9