CVE-2025-56005
CRITICALPLY 3.11 yacc picklefile - Unsafe Pickle Deserialization Code Execution
Title source: manualExploitation Summary
EIP tracks 2 public exploits for CVE-2025-56005. PoCs published by bohmiiidd, tom025.
AI-analyzed exploit summary This repository provides a valid proof-of-concept for CVE-2025-56005, demonstrating an unsafe deserialization vulnerability in PLY (Python Lex-Yacc) that leads to arbitrary code execution via pickle deserialization.
Description
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.
Exploits (2)
This repository provides a valid proof-of-concept for CVE-2025-56005, demonstrating an unsafe deserialization vulnerability in PLY (Python Lex-Yacc) that leads to arbitrary code execution via pickle deserialization.
This repository argues against the validity of CVE-2025-56005 by demonstrating that the provided PoC fails to execute successfully and does not demonstrate arbitrary code execution. The code attempts to exploit a deserialization vulnerability in PLY 3.11 but results in an AttributeError.
References (10)
Scores
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H