CVE-2005-2875: Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles
CVE-2005-2875 is a high-severity flaw (CVSS 7.5) affecting py2play. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles and executes.
Why this priority
- High severity
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.5 (High) |
| EPSS exploit chance | 1.9% (top 20%) |
| CISA exploited list | No |
| Published | 2005-09-13 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2005-2875?
py2play: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2005-2875 being exploited?
CVE-2005-2875 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2005-2875 affect?
CVE-2005-2875 affects py2play. Severity is high (CVSS 7.5). Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles and executes.
How urgent is CVE-2005-2875?
Priority 46/100. High severity