pypickle unsafe deserialization vulnerability
Published May 26, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
pypickle unsafe deserialization vulnerability
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- VDB-310262 | erdogant pypickle pypickle.py load deserialization ↗
- VDB-310262 | CTI Indicators (IOB, IOC, IOA) ↗
- Submit #579157 | erdogant pypickle 1.1.5 Insecure Deserialization ↗
- Source repository ↗
- Source repository ↗
- Patch commit ↗
- Source repository ↗
Record history
Published May 26, 2025 · Last refreshed Nov 3, 2026