Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2025-56005

Quick assessment

Affected
n/a n/a
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

PLY是B07个人开发者的一个Python库。 PLY 3.11版本存在安全漏洞，该漏洞源于yacc函数的picklefile参数未经验证地反序列化pickle文件，可能导致远程代码执行。

AI Predicted 9.8 Difficulty: Easy EPSS 17.15% · P97

Affected Version Matrix 1

VendorProduct Version RangeStatus
n/a n/a n/a affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2025-56005

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
PLY 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
PLY是B07个人开发者的一个Python库。 PLY 3.11版本存在安全漏洞，该漏洞源于yacc函数的picklefile参数未经验证地反序列化pickle文件，可能导致远程代码执行。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
- n/a n/a -

II. Public POCs for CVE-2025-56005

# POC Description Source Link Shenlong Link
1 Arguments to reject CVE-2025-56005 https://github.com/tom025/ply_exploit_rejection POC Details
2 Clarification Regarding the Rejection Arguments https://github.com/bohmiiidd/Undocumument_RCE_PLY-yacc-CVE-2025-56005 POC Details
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-56005

请登录查看更多情报信息。

Proof of Concept for CVE-2025-56005 (1)

Same Patch Batch · n/a · 2026-01-20 · 20 CVEs total

CVE-2026-1202 7.3 HIGH CRMEB LoginController.php appleLogin improper authentication
CVE-2026-1203 5.6 MEDIUM CRMEB JSON Token LoginServices.php remoteRegister improper authentication
CVE-2026-1195 5.0 MEDIUM MineAdmin JWT Token refresh data authenticity
CVE-2026-1197 3.1 LOW MineAdmin downloadById information disclosure
CVE-2026-1196 3.1 LOW MineAdmin getFileInfoById information disclosure
CVE-2025-57156 OwnTone 安全漏洞
CVE-2025-57155 OwnTone 安全漏洞
CVE-2025-63647 OwnTone 安全漏洞
CVE-2025-63648 OwnTone 安全漏洞
CVE-2025-66902 Websocket Server 安全漏洞
CVE-2025-66692 Trust Wallet Core 安全漏洞
CVE-2025-66803 Turbo 安全漏洞
CVE-2025-55423 EFM ipTIME Routers 安全漏洞
CVE-2025-67263 Abacre Retail Point of Sale 安全漏洞
CVE-2025-67261 Abacre Retail Point of Sale 安全漏洞
CVE-2025-56353 tinyMQTT 安全漏洞
CVE-2025-65482 XDocReport 安全漏洞
CVE-2025-64087 XDocReport 安全漏洞
CVE-2025-67824 The Starware WorklogPRO - Jira Timesheets 安全漏洞

IV. Related Vulnerabilities

Same product: n/a
Same vendor: n/a

V. Comments for CVE-2025-56005

No comments yet

Leave a comment