CVE-2025-5175: A vulnerability was found in erdogant pypickle up to 1.1.5

Q: How do I fix CVE-2025-5175?

pypickle: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-5175 being exploited?

CVE-2025-5175 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-5175 affect?

CVE-2025-5175 affects pypickle. Severity is medium (CVSS 5.3). 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 authorization. Attacking locally is a requir

Q: How urgent is CVE-2025-5175?

Priority 28/100. Public exploit reference

Routine

MEDIUM 5.3UPGRADE

CVE-2025-5175 is a medium-severity flaw (CVSS 5.3) affecting pypickle. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 authorization. Attacking locally is a requirement. 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 named 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to u

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 84%)
CISA exploited list	No
Weakness	CWE-266, CWE-285
Published	2025-05-26
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: erdogant

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-26 08:15 UTCPublished CVE record published
2026-06-17 09:47 UTCUpdated Record last modified

erdogant pypickle UPGRADE

Affected: < 2.0.0

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pypickle || rpm -q pypickle || pypickle --version

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pypickle

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pypickle

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-5175?

pypickle: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2025-5175 being exploited?

CVE-2025-5175 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-5175 affect?

CVE-2025-5175 affects pypickle. Severity is medium (CVSS 5.3). 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 authorization. Attacking locally is a requir

How urgent is CVE-2025-5175?

Priority 28/100. Public exploit reference

Related CVEs

CVE-2025-5174 MEDIUM 5.3 UPGRADE A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic

References

← Back to latest CVEs