# A vulnerability was identified in PyTorch 2.10.0. The affected element is an unknown function of the component pt2 Loading Handler. The manipulation leads to deserialization. The attack can only be...

Advisory record · `PYSEC-2026-139`

- **Identifiers:** `PYSEC-2026-139` · `BIT-pytorch-2026-4538` · `CVE-2026-4538`
- **State:** Confirmed
- **Severity:** CVSS 4.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 22 Mar 2026
- **Updated:** 21 May 2026
- **Reviewed by a person:** No

Published by OSV at 22 Mar 2026, 05:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `torch` (PyPI): affected `<=2.10.0`; no fixed version yet

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

- 4.8 Medium, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`, from CNA (VulDB)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 16th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of OSV, published 22 Mar 2026. New records show when each source confirmed them.

## Sources

- [OSV: PYSEC-2026-139](https://osv.dev/vulnerability/PYSEC-2026-139)
- <https://github.com/pytorch/pytorch/>
- <https://vuldb.com/?id.352326>
- <https://vuldb.com/?submit.774681>
- <https://github.com/pytorch/pytorch/pull/176791>

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/PYSEC-2026-139>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-139/>. Everything for agents: <https://agentprime.io/llms.txt>.