CVE-2025-5174Public exploit

Local code execution via unvalidated pickle loading

Published May 26, 2025 · Updated May 28, 2025

Unsafe deserialization in erdogant pypickle 1.1.0 through 1.1.5 allows local users to execute arbitrary code through a crafted pickle file. The load function in pypickle/pypickle.py passes file contents to pickle.load without validating the serialized object graph, allowing reduce handlers to invoke attacker-chosen callables. Exploitation requires local control of a pickle file that a Python process loads; code runs with that process's permissions.

CVSS severity7.8
High
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Unsafe deserialization in erdogant pypickle 1.1.0 through 1.1.5 allows local users to execute arbitrary code through a crafted pickle file. The load function in pypickle/pypickle.py passes file contents to pickle.load without validating the serialized object graph, allowing reduce handlers to invoke attacker-chosen callables. Exploitation requires local control of a pickle file that a Python process loads; code runs with that process's permissions.

The record

CVE
CVE-2025-5174
Published
May 26, 2025
Updated
May 28, 2025
Vendor
erdogant
Product
pypickle
Classifications
CWE-20, CWE-502, T1059.006
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 26, 2025CVE publishedPublication date reported by the CVE source.
  2. May 28, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.1.0
  2. Affected versionversion=1.1.1
  3. Affected versionversion=1.1.2
  4. Affected versionversion=1.1.3
  5. Affected versionversion=1.1.4
  6. Affected versionversion=1.1.5

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

erdogant · pypickleversion=1.1.0; version=1.1.1; version=1.1.2; version=1.1.3; version=1.1.4; version=1.1.5

Published CVSS scores

4.3VulDBAV:L/AC:L/Au:S/C:P/I:P/A:P
7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5.3VulDBCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.8VulDBCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-20Improper Input Validation
CWE-502Deserialization of Untrusted Data
T1059.006Python

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo