Technology · PyPI
picklescan (PyPI) vulnerabilities
Updated . Rebuilt every hour.
Junglewise Threat Intelligence has tracked 74 vulnerabilities in picklescan (PyPI): 0 in the last 7 days and 24 in the last 90 days, 16 of them critical and 0 exploited in the wild. The most recent, CVE-2025-71375, was published on 4 July 2026.
- Last 7 days
- 0
- Last 90 days
- 24
- Critical, all time
- 16
- Exploited in the wild
- 0
About picklescan (PyPI)
A security tool for scanning Python pickle files for malicious code.
Latest picklescan (PyPI) vulnerabilities
- CVE-2025-71375: picklescan detection bypass via _operator.methodcallerhighCVSS 8.1EPSS 0.5%
- CVE-2025-71373: picklescan security bypass via operator.methodcallerhighCVSS 8.1EPSS 0.6%
- CVE-2025-71372: Picklescan detection bypass via numpy getlincoef gadgethighCVSS 8.1EPSS 0.5%
- CVE-2025-71369: picklescan safety check bypass via PyTorch decoder basichandlershighCVSS 8.1EPSS 0.6%
- CVE-2025-71367: picklescan security bypass via _operator.attrgetter function callhighCVSS 8.1EPSS 0.6%
- CVE-2025-71366: picklescan security bypass via torch.utils.bottleneck in pickle fileshighCVSS 8.1EPSS 0.6%
- CVE-2025-71364: picklescan detection bypass in asyncio unix_eventshighCVSS 8.1EPSS 0.8%
- CVE-2025-71362: picklescan detection bypass in numpy.f2py.crackfortranhighCVSS 8.1EPSS 0.4%
- CVE-2025-71360: picklescan detection bypass via idlelib.calltip.get_entityhighCVSS 8.1EPSS 0.4%
- CVE-2025-71359: picklescan detection bypass via lib2to3 Grammar.loadshighCVSS 8.1EPSS 0.6%
- CVE-2025-71356: picklescan detection bypass in torch.fx.experimental.symbolic_shapeshighCVSS 8.1EPSS 0.4%
- CVE-2025-71353: picklescan detection bypass via torch._dynamo.guards.GuardBuilder.gethighCVSS 8.1EPSS 0.4%
- CVE-2025-71347: picklescan security bypass via numpy.f2py.crackfortran.param_evalhighCVSS 8.1EPSS 0.6%
- CVE-2025-71345: picklescan detection bypass via torch.utils.bottleneckhighCVSS 8.1EPSS 0.6%
- CVE-2025-71343: picklescan detection bypass via lib2to3 ParserGeneratorhighCVSS 8.1EPSS 0.4%
- CVE-2025-71342: picklescan detection bypass via idlelib.run.Executive.runcodehighCVSS 8.1EPSS 0.6%
- CVE-2025-71374: picklescan detection bypass via profile.Profile.runhighCVSS 8.1EPSS 0.6%
- CVE-2025-71371: picklescan detection bypass via code.InteractiveInterpreter.runcodehighCVSS 8.1EPSS 0.5%
- CVE-2025-71368: picklescan detection bypass via doctest.debug_scripthighCVSS 8.1EPSS 0.8%
- CVE-2025-71363: picklescan code execution bypass via cProfile.run in pickle reducehighCVSS 8.1EPSS 0.6%
- CVE-2025-71355: Picklescan detection bypass via unsafe Numpy functionsmediumCVSS 4EPSS 0.6%
- CVE-2025-71352: picklescan detection bypass via trace.Trace.runctxhighCVSS 8.1EPSS 0.6%
- CVE-2025-71350: picklescan detection bypass via torch.utils.collect_env.runhighCVSS 8.1EPSS 0.4%
- CVE-2025-71349: picklescan detection bypass via trace.Trace.run functionhighCVSS 8.1EPSS 0.6%
- CVE-2025-71340: picklescan detection bypass in idlelib.pyshell.ModifiedInterpreter.runcodehighCVSS 8.1EPSS 0.4%
Most severe picklescan (PyPI) vulnerabilities
Exploited in the wild first, then by severity and CVSS score.
- CVE-2026-3490: picklescan blocklist bypass via pkgutil.resolve_namecriticalCVSS 10EPSS 0.9%
- PickleScan blocklist bypass via pkgutil.resolve_namecriticalCVSS 10
- CVE-2026-56315: picklescan remote code execution via unblocked standard library modulescriticalCVSS 9.8EPSS 1.1%
- CVE-2026-53874: picklescan unsafe deserialization via obfuscated eval callcriticalCVSS 9.8EPSS 0.8%
- CVE-2025-71323: picklescan remote code execution via unblocked ctypes modulecriticalCVSS 9.8EPSS 0.8%
- CVE-2026-53873: picklescan incomplete blocklist bypass in profile modulecriticalCVSS 9.8EPSS 0.7%
- CVE-2025-71321: Picklescan arbitrary file write via distutils blocklist bypasscriticalCVSS 9.8EPSS 0.6%
- CVE-2025-71320: picklescan incomplete deny-list bypass leading to RCEcriticalCVSS 9.8EPSS 0.6%
- CVE-2025-71325: picklescan detection bypass in STACK_GLOBAL opcode parsingcriticalCVSS 9.8EPSS 0.5%
- PickleScan incomplete blocklist RCE via stdlib modulescriticalCVSS 9.8
Vulnerabilities per week
The last 13 weeks, by the week each vulnerability was published.
| Week of | Bar | Vulns | Critical |
|---|---|---|---|
| 29 Jun 2026 | 24 | 0 | |
| 6 Jul 2026 | 0 | 0 | |
| 13 Jul 2026 | 0 | 0 | |
| 20 Jul 2026 | 0 | 0 | |
| 27 Jul 2026 | 0 | 0 | |
| 3 Aug 2026 | 0 | 0 | |
| 10 Aug 2026 | 0 | 0 | |
| 17 Aug 2026 | 0 | 0 | |
| 24 Aug 2026 | 0 | 0 | |
| 31 Aug 2026 | 0 | 0 | |
| 7 Sep 2026 | 0 | 0 | |
| 14 Sep 2026 | 0 | 0 | |
| 21 Sep 2026 | 0 | 0 |
How this is built
Junglewise Threat Intelligence collects vulnerabilities from NVD, GitHub Security Advisories, OSV, the CISA Known Exploited Vulnerabilities catalog, FIRST EPSS and vendor advisories, and matches each one to the technologies and vendors it affects. Dates are the date a vulnerability was published, in UTC.
The pages are rebuilt from the database every hour. Frozen weekly and monthly reports never change once published, so they can be cited.
Use this data
The same data is at https://junglewise.ai/threats/technologies/picklescan.json, for scripts and language models. It is free to reuse under CC BY 4.0 with a link back to this page.
Cite as: Junglewise Threat Intelligence, "picklescan (PyPI) vulnerabilities", https://junglewise.ai/threats/technologies/picklescan, 26 September 2026.