CVE-2025-56005 Details
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.
A remote code execution vulnerability has been identified in the PLY (Python Lex-Yacc) library, specifically in version 3.11 distributed through PyPI. The issue arises from an undocumented feature that allows the `yacc()` function to accept a `.pkl` file via the `picklefile` parameter. This file is deserialized using `pickle.load()` without any validation. Since the `pickle` module can execute embedded code during deserialization, an attacker can exploit this by crafting a malicious pickle file that executes arbitrary code when the parser is initialized. The vulnerability is particularly concerning because the `picklefile` parameter is not mentioned in the official documentation or the GitHub repository, yet it is active in the PyPI version. This creates a stealthy backdoor and a risk of persistence, especially in environments where parser tables are cached, shared, or loaded from user-controlled paths.
Users are advised not to use the `picklefile` parameter with untrusted or externally writable files, and to avoid loading parser tables from user-controlled locations. All pickle files should be treated as unsafe input, and it is recommended to regenerate parser tables instead of loading them from disk.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 20, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-502 | Deserialization of Untrusted Data | redhat-SADP |
| CWE-502 | Deserialization of Untrusted Data | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| dabeaz ply | 3.11 |
CPE
Remediation
| |
Change History
22 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 17, 2026 | CVE Modified | [email protected] |
| Sep 17, 2026 | CVE Modified | CVE |
| Sep 17, 2026 | CVE Modified | redhat-SADP |
| Aug 24, 2026 | CVE Modified | redhat-SADP |
| Aug 7, 2026 | CVE Modified | redhat-SADP |
| Jul 20, 2026 | CVE Modified | redhat-SADP |
| Jul 15, 2026 | CVE Modified | redhat-SADP |
| Jun 30, 2026 | CVE Modified | redhat-SADP |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Feb 6, 2026 | CVE Modified | [email protected] |
| Jan 30, 2026 | CVE Modified | CVE |
| Jan 30, 2026 | Initial Analysis | [email protected] |
| Jan 29, 2026 | CVE Modified | CVE |
| Jan 29, 2026 | CVE Modified | CVE |
| Jan 29, 2026 | CVE Modified | CVE |
| Jan 28, 2026 | CVE Modified | [email protected] |
| Jan 28, 2026 | CVE Modified | [email protected] |
| Jan 23, 2026 | CVE Modified | CVE |
| Jan 23, 2026 | CVE Modified | CVE |
| Jan 20, 2026 | CVE Modified | CISA-ADP |
| Jan 20, 2026 | New CVE Received | [email protected] |