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.
Timeline
Days relative to CVE publicationFirst public PoC 251 days after publication; not in CISA KEV. First PoC: gdfurr98/ply-safepickle (created 27 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs · 1 pending · 1 not a PoC
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| gdfurr98/ply-safepickle | 27 Sep 2026 +251 d | 0 | PoC via PoC Index |
| gdfurr98/ply-cve-2025-56005-lab | 27 Sep 2026 +251 d | 0 | PoC |
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| bohmiiidd/Undocumument_RCE_PLY-yacc-CVE-2025-56005 | unknown | 0 | Pending · repository unavailable (HTTP 404) |
Not a PoC 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| tom025/ply_exploit_rejection | 27 Jan 2026 +7.5 d | 0 | Not a PoC · unrelated |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.