How severe is CVE-2005-2875?

No CVSS score has been assigned to CVE-2005-2875 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2005-2875?

CVE-2005-2875 affects the following packages: py2play (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2005-2875?

The records we use list no patched version of py2play for CVE-2005-2875. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2005-2875 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for py2play, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2005-2875 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2005-2875 actively exploited in the wild?

No public exploit code has been indexed for CVE-2005-2875 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2005-2875?

CVE-2005-2875 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2005-2875 published, and has it been updated?

CVE-2005-2875 was published on May 1, 2022 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2005-2875 — py2play

CVE-2005-2875 is a security vulnerability in py2play. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Py2Play Unpickles Untrusted Objects

Also known asPYSEC-2026-742

Published

May 1, 2022

Updated

Jul 6, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍py2play

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles and executes.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`py2play`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

py2playpy2play

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for py2play, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of py2play for CVE-2005-2875. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Py2Play allows remote attackers to execute arbitrary Python code via pickled objects, which Py2Play unpickles and executes.

O3 Security · Impact-Aware SCA

Is CVE-2005-2875 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works