# Picklescan missing detection when calling pytorch function torch.jit.unsupported_tensor_ops.execWrapper

Advisory record · `GHSA-vr7h-p6mm-wpmh`

- **Identifiers:** `GHSA-vr7h-p6mm-wpmh` · `CVE-2025-71370` · `PYSEC-2026-4136`
- **State:** Confirmed
- **Severity:** CVSS 7.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 22 Aug 2025
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Aug 2025, 16:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `picklescan` (PyPI): affected `<0.0.28`; fixed in `0.0.28`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Picklescan versions before 0.0.28 fail to flag pickle files that call torch.jit.unsupported_tensor_ops.execWrapper, a PyTorch function that can execute code. An attacker can craft a malicious pickle file that Picklescan reports as safe, and if a victim loads it with pickle.load(), remote code execution can follow. Upgrade picklescan to version 0.0.28 or later.

Written 1 Nov 2026.

## 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

- 7.6 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0048, the 41st percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vr7h-p6mm-wpmh)

## Sources

- [GitHub Advisory Database: GHSA-vr7h-p6mm-wpmh](https://github.com/advisories/GHSA-vr7h-p6mm-wpmh)
- [OSV: GHSA-vr7h-p6mm-wpmh](https://osv.dev/vulnerability/GHSA-vr7h-p6mm-wpmh)
- <https://github.com/mmaitre314/picklescan/security/advisories/GHSA-vr7h-p6mm-wpmh>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-71370>
- <https://github.com/mmaitre314/picklescan/pull/47>
- <https://github.com/mmaitre314/picklescan/commit/7f994d62084fe43f1cffdef2f9bae6923344ef53>
- <https://github.com/mmaitre314/picklescan>
- <https://github.com/mmaitre314/picklescan/releases/tag/v0.0.28>
- <https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-torch-jit-unsupported-tensor-ops-execwrapper>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vr7h-p6mm-wpmh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vr7h-p6mm-wpmh/>. Everything for agents: <https://agentprime.io/llms.txt>.