No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 23 Oct 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pylint-dev
Pylint-dev pylint |
|
| Vendors & Products |
Pylint-dev
Pylint-dev pylint |
|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Thu, 22 Oct 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Pylint: Arbitrary code execution via pickle deserialization of the stats cache in PYLINT_HOME | |
| Weaknesses | CWE-502 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-22T16:50:02.569Z
Reserved: 2026-10-21T20:34:25.599Z
Link: CVE-2026-114608
No data.
Status : Deferred
Published: 2026-10-22T17:16:58.750
Modified: 2026-10-22T17:40:46.877
Link: CVE-2026-114608
OpenCVE Enrichment
Updated: 2026-10-22T21:19:01Z