Quick answers
- Is CVE-2025-71348 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71348 being exploited in the wild.
- How severe is CVE-2025-71348?
- High severity, with a CVSS score of 8.1, published 21 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) <= 0.0.27, ECOSYSTEM:introduced=0,fixed=0.0.28.
- Is there a fix for CVE-2025-71348?
- Yes. picklescan (PyPI): upgrade to 0.0.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71348 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71348?
- Check whether you run picklescan (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- picklescan (PyPI): upgrade to 0.0.28 or later
pip install "picklescan>=0.0.28"
Technical details
This vulnerability is a detection bypass in the Picklescan library (CWE-345: Insufficient Verification of Data Authenticity). The root cause is that Picklescan fails to recognize torch.utils._config_module.load_config as a dangerous function when called via the pickle __reduce__ method. An attacker crafts a pickle payload that calls load_config with a malicious nested pickle as an argument; when Picklescan scans this file, it does not flag it as dangerous, allowing the victim to call pickle.load() and trigger remote code execution. The attack requires no authentication or privileges, relies on network delivery of the pickle file, and requires user interaction (victim must check and then load the file). The vulnerability affects Picklescan versions ≤ 0.0.27 and is fixed in 0.0.28.
Affected products
- mmaitre314 picklescan <= 0.0.27
Identifiers
- CVE-2025-71348
- GHSA-vv6j-3g6g-2pvj
- PYSEC-2026-245
Timeline
- 2025-08-22: disclosed: Vulnerability published to GitHub Advisory Database
- 2025-08-22: patched: Fix released in Picklescan 0.0.28