Picklescan is vulnerable to RCE via missing detection when calling numpy.f2py.crackfortran.getlincoef
GHSA-rrxm-2pvv-m66x · published 2025-12-30
- Severity
- High
- CVSS score
- 8.2
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 0.0.33
Arbitrary code execution on the victim machine once they load the “scanned as safe” pickle / model file. Affects any workflow relying on Picklescan to vet untrusted pickle / PyTorch artifacts. Enables supply‑chain poisoning of shared model files.
Upgrade picklescan to 0.0.33 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| picklescan | PyPI | < 0.0.33 | 0.0.33 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalPickleScan's profile.run blocklist mismatch allows exec() bypasspicklescan
- CriticalPickleScan has multiple stdlib modules with direct RCE not in blocklistpicklescan
- CriticalPickleScan's pkgutil.resolve_name has a universal blocklist bypasspicklescan
- CriticalPicklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Importspicklescan
- CriticalPicklescan Bypass is Possible via File Extension Mismatchpicklescan
- CriticalPicklescan: ZIP archive scan bypass is possible through non-exhaustive Cyclic Redundancy Checkpicklescan
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.