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

Advisory record · `GHSA-22qq-2fwx-7p67`

- **Identifiers:** `GHSA-22qq-2fwx-7p67` · `CVE-2026-114608`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Oct 2026, 14:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pylint` (PyPI): affected `<4.0.9`; fixed in `4.0.9`

## 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.

Written 31 Oct 2026.

## 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

- 5.4 Medium, CVSS 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`, from 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](https://osv.dev/vulnerability/GHSA-22qq-2fwx-7p67)

## Sources

- [GitHub Advisory Database: GHSA-22qq-2fwx-7p67](https://github.com/advisories/GHSA-22qq-2fwx-7p67)
- [OSV: GHSA-22qq-2fwx-7p67](https://osv.dev/vulnerability/GHSA-22qq-2fwx-7p67)
- <https://github.com/pylint-dev/pylint/security/advisories/GHSA-22qq-2fwx-7p67>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-114608>
- <https://github.com/pylint-dev/pylint/commit/58c87cffca9de2b3e89aa07b89686cbc90cfea2d>
- <https://github.com/pylint-dev/pylint/commit/5b241f66318220e9ba7b21ca631fbfe8e77682ca>
- <https://github.com/pylint-dev/pylint>
- <https://github.com/pylint-dev/pylint/releases/tag/v4.0.9>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-22qq-2fwx-7p67>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-22qq-2fwx-7p67/>. Everything for agents: <https://agentprime.io/llms.txt>.