Skip to content
Fencer Vulns
medium 5.4

CVE-2026-114608 json

Pylint: Arbitrary code execution via pickle deserialization of the stats cache in PYLINT_HOME

published 2026-10-22 18 d ago modified 2026-10-29 11 d ago also GHSA-22qq-2fwx-7p67 , EUVD-2026-108257

cvss
5.4
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi pylint 4.0.9
  • pylint Debian 14 4.0.9-1

debian advisories DEBIAN-CVE-2026-114608

  • python-pylint openSUSE Tumbleweed 4.1.3-1.1

opensuse advisories openSUSE-SU-2026:12392-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-114608 updated cvss 6.7

pylint: pylint: Arbitrary code execution via untrusted cache deserialization

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9, rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9, rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9, +1 more Red Hat Service Telemetry Framework 1.5 stf/prometheus-webhook-snmp-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
11 d ago

Exploit prediction

0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 5.4 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 4.0 5.4 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
pypi pylint
<4.0.9
4.0.9

Affected products

  • pylint-dev pylint

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.