Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Py2Play Unpickles Untrusted Objects

CVE-2005-2875GHSA-wcpc-f63g-x26q

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI py2play

    Affected
    <= 0.1.8
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2005-2875: 1.91% estimated exploitation activity in the next 30 days; percentile 79.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-wcpc-f63g-x26q

  2. Revision 1 · created ·

    Published from osv record GHSA-wcpc-f63g-x26q

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2005-2875

Advisory: Py2Play Unpickles Untrusted Objects
IDs: CVE-2005-2875, GHSA-wcpc-f63g-x26q
Record: https://patchnext.com/advisories/cve-2005-2875 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI py2play: affected <= 0.1.8

## Suggested inspection (read-only)
- `python -m pip show py2play`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on py2play.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wcpc-f63g-x26q (OSV record GHSA-wcpc-f63g-x26q lists affected ranges: PyPI py2play >=0 <=0.1.8)
- Verified: https://github.com/advisories/GHSA-wcpc-f63g-x26q (GitHub-reviewed advisory GHSA-wcpc-f63g-x26q lists affected ranges: PyPI py2play >=0 <=0.1.8)

Commands are suggestions: review each one before running it.

Loading voting…