Skip to main content

CVE-2026-114608: CWE-502: Deserialization of Untrusted Data in pylint-dev pylint

0
Medium
VulnerabilityCVE-2026-114608cvecve-2026-114608cwe-502
Published: 10/22/2026 (10/22/2026, 16:50:02 UTC)
Source: CVE Database V5
Vendor/Project: pylint-dev
Product: pylint

Description

Pylint versions from 0.15.2 up to but not including 4.0.9 have a vulnerability where module statistics are stored in predictable cache files and loaded using pickle.load. An attacker with write access to the cache directory can replace these files with malicious serialized data, leading to arbitrary code execution with the privileges of the user running Pylint. The default per-user cache is typically not writable by others. This issue is fixed in version 4.0.9.

CVSS v4.0

Score 5.4medium

Attack Vector
Local
Attack Complexity
High
Attack Requirements
Present
Privileges Required
Low
User Interaction
Passive
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

pylint-dev

pylint

Affected versions
<4.0.9
pylint
pkg:pypi/pylint
Affected versions
<4.0.9

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/22/2026, 17:15:18 UTC

Technical Analysis

Pylint, a Python static code analyzer, versions 0.15.2 through 4.0.8 store module statistics in predictable files under PYLINT_HOME and deserialize them using pickle.load on subsequent runs. If an attacker can write to a shared or group-writable cache directory, they can replace the stats cache with crafted serialized data. This leads to arbitrary code execution with the privileges of the user running Pylint. The default per-user cache directory is generally not writable by other users, limiting exposure. The vulnerability is addressed in Pylint version 4.0.9.

Potential Impact

An attacker able to write to a shared or group-writable cache directory can execute arbitrary code with the privileges of the user running Pylint. This could lead to privilege escalation or unauthorized code execution on the affected system. However, the default per-user cache directory is usually not writable by others, reducing the risk in typical configurations.

Mitigation Recommendations

Upgrade Pylint to version 4.0.9 or later, where this vulnerability is fixed. Until then, ensure that cache directories used by Pylint are not writable by untrusted users or groups to prevent exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-10-21T20:34:25.599Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ada415d4d27ba8daa69155e

Added to database: 10/22/2026, 17:01:17 UTC

Last enriched: 10/22/2026, 17:15:18 UTC

Last updated: 10/22/2026, 17:18:01 UTC

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses