CVE-2025-71378: picklescan before 0.0.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowin

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

picklescan: upgrade to 0.0.30. Exact commands for each OS are on this page.

Q: Is CVE-2025-71378 being exploited?

CVE-2025-71378 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-71378 affect?

CVE-2025-71378 affects picklescan. Severity is high (CVSS 8.1). picklescan before 0.0.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowing attackers to execute arbitrary code. Malicious pickle files bypass picklescan detection and execute remote code when loaded via

Q: How urgent is CVE-2025-71378?

Priority 44/100. High severity; Public exploit reference

This month

HIGH 8.1UPGRADE

CVE-2025-71378 is a high-severity flaw (CVSS 8.1) affecting picklescan. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

picklescan before 0.0.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowing attackers to execute arbitrary code. Malicious pickle files bypass picklescan detection and execute remote code when loaded via pickle.load().

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-06-21
Last modified	2026-10-12

Publisher (CNA): VulnCheck · Vendor: mmaitre314

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

Am I affected?

Timeline

2026-06-21 14:16 UTCPublished CVE record published
2026-10-12 22:10 UTCUpdated Record last modified

mmaitre314 picklescan UPGRADE

Affected: < 0.0.30

Fixed in: 0.0.30

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 0.0.30 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade picklescan

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-71378?

picklescan: upgrade to 0.0.30. Exact commands for each OS are on this page.

Is CVE-2025-71378 being exploited?

CVE-2025-71378 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-71378 affect?

CVE-2025-71378 affects picklescan. Severity is high (CVSS 8.1). picklescan before 0.0.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowing attackers to execute arbitrary code. Malicious pickle files bypass picklescan detection and execute remote code when loaded via

How urgent is CVE-2025-71378?

Priority 44/100. High severity; Public exploit reference

Related CVEs

CVE-2025-71348 HIGH 8.1 UPGRADE picklescan before 0.0.28 fails to detect malicious pickle files that invoke torch.utils._config_module.load_co
CVE-2025-71357 HIGH 8.1 UPGRADE picklescan before 0.0.30 fails to detect malicious pickle files using idlelib.pyshell.ModifiedInterpreter.runc
CVE-2026-56304 MEDIUM 6.5 UPGRADE picklescan before 1.0.1 contains an unsafe pickle deserialization vulnerability allowing unauthenticated attac

References

← Back to latest CVEs