Deserialization in Dabeaz Ply

CVE-2025-56005

An undocumented and unsafe feature in the PLY (Python Lex-Yacc) library 3.11 allows Remote Code Execution (RCE) via the `picklefile` parameter in the `yacc()` function. This parameter accepts a `.pkl` file that is deserialized with `pickle.load()` without validation. Because `pickle` allows execution of embedded code via `__reduce__()`, an attacker can achieve code execution by passing a malicious pickle file. The parameter is not mentioned in official documentation or the GitHub repository, yet it is active in the PyPI version. This introduces a stealthy backdoor and persistence risk. NOTE: A third-party states that this vulnerability should be rejected because the proof of concept does not demonstrate arbitrary code execution and fails to complete successfully.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS 0.188, 97.3th percentile (last changed ); unchanged over 30 days. About EPSS.

Affected products

Weakness classification (CWE)

Public exploits and proof-of-concept code

4 public repositories with exploit or proof-of-concept code for this CVE:

  • gdfurr98/ply-cve-2025-56005-lab (last pushed 2026-09-27): Lab demonstrating that CVE-2025-56005 is real and does allow arbitrary code execution at a minimum (the debate about RCE notwithstanding here), and shows that ply-safepickle does block the exploit pa…
  • gdfurr98/ply-safepickle (last pushed 2026-09-27): This is a modified version of PLY 3.11, from PyPI (current defunct git repo is not current to PyPI) which reimplements the pickle function in yacc.py to resolve CVE-2025-56005.
  • bohmiiidd/Undocumument_RCE_PLY-yacc-CVE-2025-56005 (last pushed 2026-01-29): Clarification Regarding the Rejection Arguments
  • tom025/ply_exploit_rejection (last pushed 2026-01-27): Arguments to reject CVE-2025-56005

References