CVE-2025-56005
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
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…
rank 20 = 18 + 0 + 0 + 2 + 0
rank@v1 · backlog
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.19069 · without this subject the record ranks 2
What it costs you if it fires
NVD CVSS base score, then the CNA's own
no CVSS held by anyone · without this subject the record ranks 20
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 20
How much of the world it touches
NVD CPE configurations
1 product in the CPE ranges · without this subject the record ranks 18
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 20
Hindsight · the state
Foresight · where to check next
This record is one instance of CWE-502, deserialization of untrusted data. The index holds 3288 prior instances of this class, 76 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1
Check a version against this record
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Proof-of-concept published · 1 public repository, 2026-01-27.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published · 1 public repository2026-01-27receipt
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
What it is stated by the CNA
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. receipt
Read the rest of the CNA's description
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.
NVD's analysis a second authority
- weakness
- CWE-502
- affected versions
- dabeaz ply 3.11
- also scored by
- 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
check it yourself github.com github.com github.com github.com receipt
Movement the material steps
Show all 18 observations
18 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The pattern, elsewhere
This record is one instance of CWE-502, deserialization of untrusted data. The index holds 3288 prior instances of this class, 76 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]
"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1
3288 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.
No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2025-56005.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.