torch vulnerabilities
Tensors and Dynamic neural networks in Python with strong GPU acceleration
- Registry
- PyPI
- Latest
- 2.15.0
31 known advisories
The latest version, 2.15.0, is not affected by any of them. Projects on older versions may be.
pip install 'torch>=2.15.0'Is your project on an affected torch?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for torch
No summary published
- Affected
- <=2.10.0
- Fixed in
- No fix released
PyTorch Vulnerable to Remote Code Execution via Untrusted Checkpoint Files
- Affected
- <2.10.0
- Fixed in
- 2.10.0
No summary published
- Affected
- <=2.5.0-NA · <=2.7.1-NA
- Fixed in
- No fix released
No summary published
- Affected
- <2.7.1
- Fixed in
- 2.7.1
No summary published
- Affected
- <2.7.1
- Fixed in
- 2.7.1
No summary published
- Affected
- <2.7.1
- Fixed in
- 2.7.1
No summary published
- Affected
- <2.9.0
- Fixed in
- 2.9.0
No summary published
- Affected
- <2.7.1
- Fixed in
- 2.7.1
No summary published
- Affected
- <2.9.0
- Fixed in
- 2.9.0
No summary published
- Affected
- <2.9.0
- Fixed in
- 2.9.0
No summary published
- Affected
- >=2.6.0 <2.7.0
- Fixed in
- 2.7.0
No summary published
- Affected
- >=2.6.0 <2.7.0
- Fixed in
- 2.7.0
No summary published
- Affected
- >=2.6.0 <2.7.0
- Fixed in
- 2.7.0
No summary published
- Affected
- >=2.6.0 <2.7.0
- Fixed in
- 2.7.0
No summary published
- Affected
- <2.7.0
- Fixed in
- 2.7.0
PyTorch: `torch.load` with `weights_only=True` leads to remote code execution
- Affected
- <2.6.0
- Fixed in
- 2.6.0
PyTorch Improper Resource Shutdown or Release vulnerability
- Affected
- <2.8.0
- Fixed in
- 2.8.0
No summary published
- Affected
- <=2.6.0-NA
- Fixed in
- No fix released
No summary published
- Affected
- <=2.6.0-NA
- Fixed in
- No fix released
PyTorch is vulnerable to memory corruption through its torch.lstm_cell function
- Affected
- <2.10.0
- Fixed in
- 2.10.0
PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence Function
- Affected
- <=2.6.0
- Fixed in
- No fix released
PyTorch is vulnerable to memory corruption through its unpack_sequence function
- Affected
- <2.9.1
- Fixed in
- 2.9.1
PyTorch is vulnerable to memory corruption through its torch.jit.script function
- Affected
- <2.13.0
- Fixed in
- 2.13.0
PyTorch susceptible to local Denial of Service
- Affected
- <2.7.1-rc1
- Fixed in
- 2.7.1-rc1
PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid Module
- Affected
- <=2.6.0
- Fixed in
- No fix released
PyTorch Tuple Handler is Vulnerable to Memory Corruption through Manipulation of None Argument
- Affected
- <=2.6.0
- Fixed in
- No fix released
No summary published
- Affected
- <2.5.0
- Fixed in
- 2.5.0
No summary published
- Affected
- <2.2.0
- Fixed in
- 2.2.0
PyTorch heap buffer overflow vulnerability
- Affected
- <2.2.0
- Fixed in
- 2.2.0
Pytorch use-after-free vulnerability
- Affected
- <2.2.0
- Fixed in
- 2.2.0
PyTorch vulnerable to arbitrary code execution
- Affected
- <1.13.1
- Fixed in
- 1.13.1
Is your torch version vulnerable?
- torch 2.15No known advisories in 2.15.0
- torch 2.14No known advisories in 2.14.1
- torch 2.13No known advisories in 2.13.0
- torch 2.121 advisory in 2.12.1
- torch 2.111 advisory in 2.11.0
- torch 2.102 advisories in 2.10.0
- torch 1.1326 advisories in 1.13.1
- torch 1.1227 advisories in 1.12.1
- torch 1.1127 advisories in 1.11.0
- torch 1.1027 advisories in 1.10.2
- torch 1.927 advisories in 1.9.1
- torch 1.827 advisories in 1.8.1
Which of your client projects still run an old torch?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.