CVE-2025-5174

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-05-26 07:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 09:47 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 4.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-05-26 07:15 UTC

Last modified

2026-06-17 09:47 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-20 · Improper input validation

Record status

Analyzed

Affected

• Erdogant Pypickle < 2.0.0

Attack profile CVSS 4.0 · 4.8

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

Low

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-5174.md and follow it. Check whether this project is affected by CVE-2025-5174. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge