PyTorch is vulnerable to memory corruption through its unpack_sequence function
A vulnerability was found in PyTorch 2.6.0. It has been rated as critical. Affected by this issue is the function torch.nn.utils.rnn.unpack_sequence. The manipulation leads to memory corruption. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. A patch is available through commit [4945180](https://github.com/pytorch/pytorch/commit/494518046816d29099b7d056a74ffa5c244fdcdd).
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-2999US | — | — | ||
A vulnerability was found in PyTorch 2.6.0. It has been rated as critical. Affected by this issue is the function torch.nn.utils.rnn.unpack_sequence. The manipulation leads to memo… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/pypa/advisory-database/tree/main/vulns/torch/PYSEC-2025-193.yamlWEB
- https://github.com/pytorch/pytorchPACKAGE
- https://github.com/pytorch/pytorch/commit/494518046816d29099b7d056a74ffa5c244fdcddWEB
- https://github.com/pytorch/pytorch/issues/149622WEB
- https://github.com/pytorch/pytorch/issues/149622#issue-2935495265WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-2999ADVISORY
- https://vuldb.com/?ctiid.302048WEB
- https://vuldb.com/?id.302048WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan