Advisory record · GHSA-qpxx-2cwh-r5vh

A vulnerability was found in erdogant pypickle up to 1.1.5. It has been classified as critical. This affects the function Save of the file pypickle/pypickle.py. The manipulation leads to improper a...

CVSS 4.8 MediumEPSS 0.0025 · 16th percentile

Published by the GitHub Advisory Database at 26 May 2025, 08:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pypicklePyPI<14b4cae704a0bb4eb6723e238f25382d847a1917 || <2.0.014b4cae704a0bb4eb6723e238f25382d847a1917, 2.0.0
Identifiers
GHSA-qpxx-2cwh-r5vh · CVE-2025-5175 · PYSEC-2025-46
Weakness (CWE)
CWE-266 · CWE-285
Published
26 May 2025
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The pypickle package versions before 2.0.0 contain a flaw in the Save function that leads to improper authorization. An attacker with local access can exploit it, and the exploit has been publicly disclosed. Upgrade pypickle to version 2.0.0 or later to fix the issue.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.8 Medium 4.0 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 CNA (VulDB)
  • CISA KEV Not listed.
  • EPSS 0.0025, the 16th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 26 May 2025. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.