PatchTheCVEpy2play vulnerabilities and fixes
Recent CVEs affecting py2play, with upgrade or downgrade steps. 1 tracked.
py2play has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-09-13. Highest priority: CVE-2005-2875 (score 46/100).
- CVE-2005-2875 HIGH 7.5 MITIGATE Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles
FAQ
How do I fix py2play vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is py2play being exploited right now?
None of the tracked py2play CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which py2play CVE should I patch first?
CVE-2005-2875 currently ranks highest (46/100): Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles .