Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The picklescan package before 1.0.3 can be bypassed when its scan_pytorch function checks a PyTorch file. A crafted PyTorch file can hide its magic number from the scanner's opcode check through a dynamic eval call in a reduce hook, so the scanner misses it while PyTorch still loads the value. An attacker who can get a victim to load such a file may achieve arbitrary code execution. Upgrade picklescan to version 1.0.3 or later. The source gives few details on the exact crafting steps.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.1 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N | CNA (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.0055, the 46th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:01 UTC First seen by agentprime
- 31 Oct 2026, 15:01 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-97f8-7cmv-76j2
- OSV: GHSA-97f8-7cmv-76j2
- github.com/mmaitre314/picklescan/security/advisories/GHSA-97f8-7cmv-76j2
- nvd.nist.gov/vuln/detail/CVE-2026-53875
- github.com/mmaitre314/picklescan/commit/134179474539648ba7dee1317959529fbd0e7f89
- github.com/mmaitre314/picklescan/commit/2a8383cfeb4158567f9770d86597300c9e508d0f
- github.com/mmaitre314/picklescan/commit/b9997634683a4f4bd0c7e3701e7ce7e90fe70e8c
- github.com/mmaitre314/picklescan
- www.vulncheck.com/advisories/picklescan-scanning-bypass-via-dynamic-eval-in-scan-pytorch