pypickle unsafe deserialization vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-5174: 0.34% estimated exploitation activity in the next 30 days; percentile 27.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic. Affected by this issue is the function load of the file pypickle/pypickle.py. The manipulation leads to deserialization. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is identified as 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.

Published by the source

26 May 2025, 09:30 UTC

Last modified by the source

4 Jun 2025, 21:29 UTC

Source last checked

26 Oct 2026, 13:32 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5qwj-342r-h886

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5qwj-342r-h886

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

# Patch Next advisory brief: CVE-2025-5174

Advisory: pypickle unsafe deserialization vulnerability
IDs: CVE-2025-5174, GHSA-5qwj-342r-h886
Record: https://patchnext.com/advisories/cve-2025-5174 (revision 3, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pypickle 2.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pypickle: affected < 2.0.0; fixed in 2.0.0

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pypickle.
- 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-5qwj-342r-h886 (OSV record GHSA-5qwj-342r-h886 lists affected ranges: PyPI pypickle >=0 <2.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-5qwj-342r-h886 (GitHub-reviewed advisory GHSA-5qwj-342r-h886 lists affected ranges: PyPI pypickle >=0 <2.0.0)

Commands are suggestions: review each one before running it.