CVE-2025-56005
Last modified
CVE-2025-56005 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 18.65% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Dabeaz | Ply | 3.11 |
References
- https://github.com/bohmiiidd/Undocumented-RCE-in-PLYExploit, Third Party Advisory
- https://github.com/bohmiiidd/Undocumument_RCE_PLY-yacc-CVE-2025-56005Exploit, Third Party Advisory
- https://github.com/tom025/ply_exploit_rejectionExploit, Mitigation, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2026/01/23/4Exploit, Mailing List
- http://www.openwall.com/lists/oss-security/2026/01/28/5Exploit, Mailing List
- http://www.openwall.com/lists/oss-security/2026/01/29/1Exploit, Mailing List
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-56005?
How severe is CVE-2025-56005?
How do I fix CVE-2025-56005?
Are you affected by CVE-2025-56005?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
