cve.bz

CVE-2026-114608 pylint-dev pylint: Deserialization of Untrusted Data

5.4 mediumEPSS 0.1%Fix available

Medium (5.4) in pylint-dev pylint. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in pylint 4.0.9.

On this page
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.

Severity

CVSS 4.0

5.4 medium
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
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-114608 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114608?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114608?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114608 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
pylint-dev pylint< 4.0.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-22qq-2fwx-7p67PyPIpylint<4.0.94.0.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13pylintno fix listedDEBIAN-CVE-2026-114608
Debian14pylint4.0.9-1DEBIAN-CVE-2026-114608
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morepylintno fix listedUBUNTU-CVE-2026-114608
openSUSETumbleweedpython-pylint4.1.3-1.1openSUSE-SU-2026:12392-1
Azure Linux3pylintno fix listedAZL-110543

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having Moderate impact for Red Hat products because exploitation requires local access and non-standard configurations where cache locations are shared or group-writable. Under default system installations, Pylint places its cache in a private user directory that is inaccessible to other unprivileged users. Consequently, an attacker can only compromise an environment if the PYLINT_HOME environment variable explicitly references a shared directory or if directory permissions have been improperly relaxed.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9Fix deferred
Service Telemetry Framework 1.5stf/prometheus-webhook-snmp-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-114608.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON